Docker - Upgrading Ignition image version while Ignition data folder is mounted to host

Ignition 8.3 Early Access
,
1

Hey All,

I configured a Docker environment with a few different services, including multiple Ignition gateways. These gateways are on 8.3 beta, and their entire /usr/local/bin/ignition/data folder is mounted to my host machine. I’m doing this (instead of using named volumes) because I have individual repositories for all those gateways, and I want to manage those local repositories from my host and not from the container. @Travis.Cox ‘s LinkedIn post on Ignition 8.3 Version control helped a lot in setting up the git environment. (Legend!)

This is all working fine, but I don’t understand how I will manage Ignition version updates for this setup. For instance, when Ignition 8.3.1 is released, I can change the Ignition image version in my docker-compose file, but the Ignition data folder with all the gateway config data would remain intact on my host machine.

Will all future Ignition versions be compatible with the Ignition data folder of older versions? It seems unlikely, since new gateway configuration options could be added to Ignition, which would reside in the data folder. What am I missing here? How does the version upgrade work when the Ignition data folder lives outside of the container?

2

Just as it would in a standard upgrade scenario that didn't involve Docker at all.

If some future version of Ignition needs to make changes or upgrades to some config data format then it'll do that when it starts up.

4 Likes
3

That’s good to know. Thanks @Kevin.Herron .

So I will just change the image version, and Ignition should take care of the file changes on the bind mount folder.

1 Like