A simple stop/start of a container will retain the Maker-only modules. To clarify a little bit, you’ll see the behavior you describe when you remove and re-create the container (which may happen quite easily if you’re using Docker Swarm (not sure if you are, but just guessing based on the secrets: usage in your compose YAML)). You’re not doing anything wrong–this is a known issue at the moment. I was trying to use the official image from Inductive, thank you for reaching out. I have not experienced this with the image maintained by Kevin Collins. # only for external connectivity to the database.Īm I doing doing something wrong? Or is there another environment variable that needs to be set?
# Note that the 1433 port doesn't need to be published here for the gateway container to connect, GATEWAY_ADMIN_PASSWORD_FILE: /run/secrets/gateway-admin-password Image: inductiveautomation/ignition:latest # You can change `latest` to a specific version, e.g. I am confused as to how this is happening. So on the restart of my container, invalid modules for Maker Edition get installed.
