We are trying to use deployment modes to program against a gateway copy of a production gateway. I have set up a docker container for the local copy, added a Dev Mode, and successfully edited the ignition.conf file to change modes. What I did not realize is if I take a gateway backup of the Dev serv…

See Docker Image | Ignition User Manual , I think this is what you want.

Here is the command portion of the compose.yaml file: command: > -n sweet-eddies -m ${GATEWAY_MAX_MEMORY:-512} I changed it to this and Ignition would not start: command: > -n sweet-eddies -m ${GATEWAY_MAX_MEMORY:-512} -Dignition.config.mode=Dev

This does work: command: > -n sweet-eddies -m ${GATEWAY_MAX_MEMORY:-512} -- wrapper.java.initmemory=512 -Dignition.config.mode=Dev Not sure why… @Kevin.Herron thanks for pointing me in the right direction.

Arguments before the double hyphen are part of the docker run command. Arguments after are passed in to the container entrypoint itself.

So I do not need the wrapper.java.initmemory=512 line. I would be great if there was an environment variable you could set instead. Thanks!!

Is it possible to edit the service start command in Windows to do the same thing?

Not exactly, but there's a different way to solve the same goal: [image] Disable devices in Gateway Startup Script (v8.3.0) Ignition Setting the deployment mode via an environment variable is not yet supported, you've got to supply the Java system property via …

Gateway Deployment Mode

Ignition

paul-griffith March 12, 2026, 5:53pm 8

Not exactly, but there's a different way to solve the same goal:

1 Like