I am doing some work with Ignition + Docker + Kubernetes and I wanted to know if it is possible to install a plugin module when spinning up an ignition container? I want to use the Tag CICD plugin to have better source control when working in Designer.

For anyone else that is looking for a solution to adding Third-Party modules, here is the docker-compose that worked for me. services: io-gateway: image: inductiveautomation/ignition:8.3.1 container_name: mqtt-gw user: "0:0" ports: - "8088:8088" - "8043:8043" envir…

Some of this might depend on what version you're using (8.1.x or 8.3.x), but you've got a few options: Build a derived image that places the module into /usr/local/bin/ignition/user-lib/modules alongside the other built-in modules. On 8.1.x, it will always be loaded if present. On 8.3.x, it will…

Thank you, the links and this information is really helpful.

Currently I have a docker compose file that is copying the third party module in along with updating the modules.json, so that ignition will be-able to detect it. The issue I am running into now is ignition is not automatically accepting the cert and license even though I am passing an environment v…

First thing I'll mention is that we @hunterdg observed a documentation error with respect to the location of user-installed modules in the Ignition 8.3 Docker image. The correct location is /usr/local/bin/ignition/data/var/ignition/modl. Modules in this location will be automatically enabled on a …

After changing the module path, ignition isn’t detecting the module. I tried composing with both /usr/local/bin/ignition/data/var/ignition/modl and /usr/local/bin/ignition/user-lib/modules and ignition still wouldn’t detect it. I checked the container with docker exec -it mqtt-gw /bin/bash and I can…

Is the compose snippet you posted complete? I didn't see a data volume, which means that it should integrate any of the .modl files from either of those folders on first-launch (since there won't be a pre-existing data/modules.json).

Ahh the compose snippet above is a previous version. this is the snippet I’ve been using: services: io-gateway: image: inductiveautomation/ignition:8.3.1 container_name: mqtt-gw user: "0:0" ports: - "8088:8088" - "8043:8043" environment: ACCEPT_IGNITION_EULA…

[image] kcollins: The correct location is /usr/local/bin/ignition/data/var/ignition/modl in OrbStack on mac, bind-mounting to this errors with the following. I get it, because the bind is creating the path with different permissions than the gateway init, but is that a bug? The Ignition Gat…

In your docker-compose do you set your user to root? user: "0:0"

well that "fixes" the issue, but no, I run it unprivileged and have sidecar containers that handle the unprivileged nature via this: user: "2003:2003" # match ignition container group_add: - 65533 # allow writing to /git this wouldn't be the first time I've seen behavior differ between Orb…

Inductive Automation Forum

Installing an Ignition Designer Plugin when spinning up a Docker Container

Ignition

hunterdg May 14, 2026, 8:28pm 15

- Merging wrapper arguments in Docker - #5 by hunterdg