Where is the ignition.conf file in a Docker container?

I set the JVM max memory in the docker command to be 2048, but when I go to /usr/local/bin/ignition/data/ignition.conf inside the container it shows that the max memory is 1024. Am I looking at the wrong file?

Docker command:

docker run -d -p 9088:8088 --name ignition-test ^
    -v gw-data:/usr/local/bin/ignition/data ^
    -e ACCEPT_IGNITION_EULA=Y ^
	-e GATEWAY_ADMIN_USERNAME=admin ^
	-e GATEWAY_ADMIN_PASSWORD=password ^
    -e IGNITION_EDITION=standard ^
	--pull always inductiveautomation/ignition:latest ^
    -n docker-test -a localhost -h 9088 -s 9043 ^
	-- wrapper.java.maxmemory=2048

Inside /usr/local/bin/ignition/data/ignition.conf:

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=1024

On the gateway webpage it shows 2048.
image

You’re not actually modifying the ignition.conf file with that command. What ends up happening is a temp file is created with any additional arguments (all the stuff after --) and wrapper.java.additional_file gets pointed at that file.

1 Like

Okay, that makes more sense. Thank you!

@kcollins1 can you confirm? That was my take after a quick read…

Any wrapper.* arguments are processed directly by the Java Service Wrapper (and will override any settings initially loaded from ignition.conf). Any other arguments are compiled into a temporary file that is referenced by the wrapper.java.additional_file setting and will be passed directly to the JVM–these are properties that you’d otherwise have to add into those numeric-indexed wrapper.java.additional.<n> lines within ignition.conf.

2 Likes