When I deploy an update, not every container contains changes. So not all containers are downloaded and restarted again (which is great, unnecessary downloading/restarting would be stupid). But I have a ElectronJS kiosk container, which connects to another container. The ElectronJS contains a placeholder until the other container is started. I’ve created a (healthcheck-)mechanism for this and that works great!
However, that container is updated 9 out of 10 times when there is a new build. This container contains a webserver with the content that has to be shown in the ElectronJS kiosk. But after an update of this container, the kiosk doesn’t restart obviously. So when there are interface changes, the user has to reboot the whole system. That is, of course, not really the nicest way to go.
So, my question is, is there a way, and what is the best way, to restart another container when the container is updated?
I’ve thought about it, and what I’ve come up with is when the webserver container starts up, it sends a request to the supervisor to restart the ElectronJS container. But that’s not necessary when the container isn’t updated. I’ve had multiple ideas, but I thought, I can better ask the experts and hear what they would do!
Thanks in advance!