JVM Startup Failed - Edge Running on Wago PFC200 (arm32) about ignition-docker HOT 2 CLOSED

I did a quick search on Wago PFC200 and came up with this website which seems to indicate that the device (Gen 2) has a maximum RAM allocation of 512MB (looks like some of the earlier models even had 256MB). You're going to be very memory-constrained on the 512MB model--Ignition won't be feasible at all on the 256MB RAM model (output of free or cat /proc/meminfo would tell you). I just took a look at the entrypoint script and it looks like the environment variables GATEWAY_INIT_MEMORY and GATEWAY_MAX_MEMORY that I have for driving the memory allocation enforces max memory at >=512MB.. Thankfully, as of kcollins/ignition:8.1.4, you can actually feed JVM/wrapper args directly through the command options on your container run, e.g.:

$ docker run -d -p 8088:8088 --privileged --name my-ignition-edge \
    -e GATEWAY_ADMIN_PASSWORD=password \
    -e IGNITION_EDITION=edge \
    kcollins/ignition:8.1.4 \
    wrapper.java.initmemory=256 \
    wrapper.java.maxmemory=384

I'd try the above first, just to see if you can get any further in the launch--it looks like, based on your logs, that the JVM probably isn't able to allocate the required default amount of memory (init of 256M, max of 1024M).

from ignition-docker.

That did the trick, thanks a lot for the quick reply.
I had to dial them back to 200 and 250 but that got the container to at least stop choking. However I couldn't get past the "gateway starting" webpage, pretty sure it's a memory/resource issue. I do have the 512MB model and was doing this mostly to see if it was possible, since I am drawn to Ignition's ability to buffer MQTT messages on the sender when the broker connection is unreliable. However it seems it isn't a realistic application for the PFC200.

from ignition-docker.