@deon.korb, I’ve not done any power-cycling yet, just got the base install setup this evening… I thought I’d share my docker run
statement, fwiw. Normally I try to use Compose, even for simple one-service setups, but I decided to just create a single, angry docker run
for this testing
:
sudo docker run -d --restart always --name ignition-maker \
-e IGNITION_EDITION=maker \
-e IGNITION_ACTIVATION_TOKEN_FILE=/run/secrets/activation-token \
-e IGNITION_LICENSE_KEY=XXXX-XXXX \
-e IGNITION_STARTUP_DELAY=300 \
-e GATEWAY_SYSTEM_NAME=Ignition-pi2 \
-e GATEWAY_ADMIN_PASSWORD_FILE=/run/secrets/gateway-password \
-e GATEWAY_MODULES_ENABLED=modbus-driver-v2,opc-ua,perspective,sql-bridge,tag-historian,udp-tcp-drivers \
-e GATEWAY_INIT_MEMORY=256 \
-e GATEWAY_MAX_MEMORY=512 \
-v ${PWD}/activation-token:/run/secrets/activation-token \
-v ${PWD}/gateway-password:/run/secrets/gateway-password \
--network host \
-v maker-data:/var/lib/ignition/data \
kcollins/ignition:8.1.0
Testing initially with 8.1.0 to see if I can replicate your findings… May I ask, did you use the Docker convenience script (referenced here in the docs) to install Docker Engine on your Pi? I’m actually starting with Balena Engine to keep things light (everything above is the same except substituting docker
with balena-engine
), but will try a vanilla Docker Engine install next if things seem to be working well here…