# Derived Image Creating Temp Admin User **URL:** \ **Category:** Ignition\ **Tags:** docker, ignition83\ **Created:** [March 12, 2026, 8:48pm UTC](https://forum.inductiveautomation.com/t/derived-image-creating-temp-admin-user/114474 "2026-03-12T20:48:43Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![derek.delizo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/derek.delizo/32/84136_2.png) [@derek.delizo](https://forum.inductiveautomation.com/u/derek.delizo)\ **Post date:** [March 12, 2026, 8:48pm UTC](https://forum.inductiveautomation.com/t/derived-image-creating-temp-admin-user/114474/1 "2026-03-12T20:48:43Z")
I am running into an issue with my derived container image. After I create the image I am passing in the Gateway admin username and password as ENV variables. When I first boot the container I can login and the temp identity provider does not get created. When I take the container down and spin it back up, a temp identity provider is created a long with a temp Admin user. I don’t understand why that is happening. I followed the [derived ignition example](https://github.com/thirdgen88/ignition-derived-example/tree/main) from github and for my case I removed a lot of the extra stuff. I am just trying to make a simple derived container with third party modules copied in. When the image isn’t derived the temp admin user and provider does not get created. Here is my Dockerfile: ```python ARG IGNITION_VERSION=8.3.1 FROM inductiveautomation/ignition:${IGNITION_VERSION} AS prep USER root # Set working directory for this prep image and ensure that exits from sub-shells bubble up and report an error WORKDIR /root # Use bash strict mode for all following RUN steps in this stage: # -e: fail on first error, -u: fail on unset vars, -o pipefail: fail if any piped command fails, # -O inherit_errexit: preserve -e behavior in subshell/command substitution contexts. SHELL ["/usr/bin/env", "-S", "bash", "-euo", "pipefail", "-O", "inherit_errexit", "-c"] COPY modules/*.modl /root/ # Final Image FROM inductiveautomation/ignition:${IGNITION_VERSION} AS final # Temporarily become root for system-level updates (required for 8.1.26+) USER root # Embed modules and base gwbk from prep image as well as entrypoint shim COPY --from=prep --chown=ignition:ignition /root/*.modl ${IGNITION_INSTALL_LOCATION}/user-lib/modules/ # Return to ignition user USER ignition # Supplement other default environment variables ENV ACCEPT_IGNITION_EULA=Y \ IGNITION_EDITION=standard \ GATEWAY_MODULES_ENABLED=all \ DISABLE_QUICKSTART=true ``` Here is the docker-compose that uses the image: ```python services: backend-gateway: image: myimage/coolgw:1.0.0 container_name: coolgw user: "0:0" ports: - "${HTTP_PORT:-8088}:8088" - "${HTTPS_PORT:-8043}:8043" command: ["-n", "tonyhawks-coolgw","-m","2048","--","wrapper.java.initmemory=2048"] environment: GATEWAY_ADMIN_USERNAME: "admin" GATEWAY_ADMIN_PASSWORD: "password" ACCEPT_MODULE_LICENSES: "com.cirruslink.mqtt.transmission.gateway,com.cirruslink.mqtt.engine.gateway,project-scan-endpoint" ACCEPT_MODULE_CERTS: "com.cirruslink.mqtt.transmission.gateway,com.cirruslink.mqtt.engine.gateway,project-scan-endpoint" volumes: - ignition_data:/usr/local/bin/ignition/data/config restart: unless-stopped volumes: ignition_data: ``` ---
**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\ **Post date:** [March 13, 2026, 1:42pm UTC](https://forum.inductiveautomation.com/t/derived-image-creating-temp-admin-user/114474/2 "2026-03-13T13:42:10Z")
Your `ignition_data` volume mount point should probably be `/usr/local/bin/ignition/data`. ---
**Author:** ![derek.delizo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/derek.delizo/32/84136_2.png) [@derek.delizo](https://forum.inductiveautomation.com/u/derek.delizo)\ **Post date:** [March 13, 2026, 4:35pm UTC](https://forum.inductiveautomation.com/t/derived-image-creating-temp-admin-user/114474/3 "2026-03-13T16:35:01Z")
In this case I am intentionally pointing it to the config folder because the end goal is to abstract out different folders under the config, so I can track it with git and create different modifications. I was running into the same issue using a bind mount and for this version I was working on I decided to use a normal docker volume to test if the same problem was occurring. ---
**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\ **Post date:** [March 17, 2026, 6:58pm UTC](https://forum.inductiveautomation.com/t/derived-image-creating-temp-admin-user/114474/4 "2026-03-17T18:58:43Z")
Independently of whether you have additional deeper mounts, you should still have a [named] volume at the root `/usr/local/bin/ignition/data` location. ---
**Author:** ![derek.delizo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/derek.delizo/32/84136_2.png) [@derek.delizo](https://forum.inductiveautomation.com/u/derek.delizo)\ **Post date:** [March 17, 2026, 9:28pm UTC](https://forum.inductiveautomation.com/t/derived-image-creating-temp-admin-user/114474/5 "2026-03-17T21:28:31Z")
@kcollins Could you please explain why? ---
**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\ **Post date:** [March 17, 2026, 9:52pm UTC](https://forum.inductiveautomation.com/t/derived-image-creating-temp-admin-user/114474/6 "2026-03-17T21:52:46Z")
There are pieces of state, such as `projects`, what might be under `data/var` as well as other files such as `commissioning.json`, `modules.json`, and others. There are additional insights on `data/var` and other folders [here](https://docs.inductiveautomation.com/docs/8.3/appendix/reference-pages/gateway-folder-structure#gateway-folder-structure) in the docs. Various systems (including third-party modules) are going to expect continuity across restarts of a given gateway via a persisted volume against `/usr/local/bin/ignition/data`.