# UI Fails to load in galaxy\_ng dev environment

**URL:** <https://forum.ansible.com/t/ui-fails-to-load-in-galaxy-ng-dev-environment/2876>\
**Category:** Get Help\
**Tags:** galaxy-ng\
**Created:** [December 13, 2023, 12:12am UTC](https://forum.ansible.com/t/ui-fails-to-load-in-galaxy-ng-dev-environment/2876 "2023-12-13T00:12:55Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![onefourfive](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/onefourfive/32/1775_2.png) [@onefourfive](https://forum.ansible.com/u/onefourfive)\
**Post date:** [December 13, 2023, 12:12am UTC](https://forum.ansible.com/t/ui-fails-to-load-in-galaxy-ng-dev-environment/2876/1 "2023-12-13T00:12:55Z")

</div>

I’m setting up galaxy\_ng in a dev environment for the first time, following steps in the docs as outlined in [dev/getting\_started](https://ansible.readthedocs.io/projects/galaxy-ng/en/latest/dev/getting_started/).

After checking out the `ansible-hub-ui` repo, running make scripts and starting with `./compose up`, I see a fatal error in the UI container:

```plaintext
ui_1 | > ansible-hub-ui@0.1.0 start-standalone
ui_1 | > NODE_ENV=development webpack serve --host 0.0.0.0 --config config/standalone.dev.webpack.config.js
ui_1 |
ui_1 | fatal: detected dubious ownership in repository at '/hub/app'
ui_1 | To add an exception for this directory, call:
ui_1 |
ui_1 | git config --global --add safe.directory /hub/app
ui_1 | [webpack-cli] Failed to load '/hub/app/config/standalone.dev.webpack.config.js' config
ui_1 | [webpack-cli] Error: Command failed: git rev-parse HEAD
ui_1 | fatal: detected dubious ownership in repository at '/hub/app'
ui_1 | To add an exception for this directory, call:
ui_1 |
ui_1 | git config --global --add safe.directory /hub/app
ui_1 |
ui_1 | at checkExecSyncError (node:child_process:890:11)
ui_1 | at execSync (node:child_process:962:15)
ui_1 | at Object.<anonymous> (/hub/app/config/webpack.base.config.js:20:3)
ui_1 | at Module._compile (node:internal/modules/cjs/loader:1356:14)
ui_1 | at Module._extensions..js (node:internal/modules/cjs/loader:1414:10)
ui_1 | at Module.load (node:internal/modules/cjs/loader:1197:32)
ui_1 | at Module._load (node:internal/modules/cjs/loader:1013:12)
ui_1 | at Module.require (node:internal/modules/cjs/loader:1225:19)
ui_1 | at require (node:internal/modules/helpers:177:18) {
ui_1 | status: 128,
ui_1 | signal: null,
ui_1 | output: [
ui_1 | null,
ui_1 | '',
ui_1 | "fatal: detected dubious ownership in repository at '/hub/app'\n" +
ui_1 | 'To add an exception for this directory, call:\n' +
ui_1 | '\n' +
ui_1 | '\tgit config --global --add safe.directory /hub/app\n'
ui_1 | ],
ui_1 | pid: 26,
ui_1 | stdout: '',
ui_1 | stderr: "fatal: detected dubious ownership in repository at '/hub/app'\n" +
ui_1 | 'To add an exception for this directory, call:\n' +
ui_1 | '\n' +
ui_1 | '\tgit config --global --add safe.directory /hub/app\n'
ui_1 | }
galaxy_ng_ui_1 exited with code 2

```

This renders the UI unreachable. What can I do to get the UI up?

---

<div class="post-metadata">

**Author:** ![himdel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/himdel/32/581_2.png) [@himdel](https://forum.ansible.com/u/himdel)\
**Post date:** [December 13, 2023, 3:20am UTC](https://forum.ansible.com/t/ui-fails-to-load-in-galaxy-ng-dev-environment/2876/2 "2023-12-13T03:20:13Z")

</div>

Try setting `HUB_UI_VERSION=whatever` in the compose environment, that should prevent webpack from trying to run `git`.

(Or you can comment out the `ANSIBLE_HUB_UI_PATH` in `.compose.env` and run the UI outside the container, `API_BASE_PATH="/api/galaxy_ng/" npm run start-standalone`.)

---

<div class="post-metadata">

**Author:** ![onefourfive](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/onefourfive/32/1775_2.png) [@onefourfive](https://forum.ansible.com/u/onefourfive)\
**Post date:** [December 19, 2023, 5:53pm UTC](https://forum.ansible.com/t/ui-fails-to-load-in-galaxy-ng-dev-environment/2876/3 "2023-12-19T17:53:10Z")

</div>

Thanks! I made this change:

```auto
HUB_UI_VERSION='4.9.0'
# and also
ANSIBLE_HUB_UI_VERSION='4.9.0'

```

However that didn’t seem to work, the `ui` container still tries to spin up with `0.1.0`. I also tried setting the env to `ANSIBLE_HUB_UI_VERSION` with the same result.

I’m trying to find the `ui` container in a compose file to see what exactly is going on, but I don’t see it in `dev/`…

---

<div class="post-metadata">

**Author:** ![onefourfive](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/onefourfive/32/1775_2.png) [@onefourfive](https://forum.ansible.com/u/onefourfive)\
**Post date:** [December 19, 2023, 8:31pm UTC](https://forum.ansible.com/t/ui-fails-to-load-in-galaxy-ng-dev-environment/2876/4 "2023-12-19T20:31:49Z")

</div>

Ok, so I think the compose file for the ui is in `dev/common/docker-compose-ui.yaml`, which doesn’t use a `HUB_UI_VERSION` env. Not sure where to proceed from here

---

<div class="post-metadata">

**Author:** ![himdel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/himdel/32/581_2.png) [@himdel](https://forum.ansible.com/u/himdel)\
**Post date:** [December 20, 2023, 2:23pm UTC](https://forum.ansible.com/t/ui-fails-to-load-in-galaxy-ng-dev-environment/2876/5 "2023-12-20T14:23:58Z")

</div>

I would suggest following the current dev development docs instead: [OCI Env Environment - Galaxy NG](https://ansible.readthedocs.io/projects/galaxy-ng/en/latest/dev/oci_env/)