Timeline for How to automatically update Swarm services when the Docker daemon restarts
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 6, 2020 at 13:35 | comment | added | BMitch |
There's no need to do a stack rm when you are doing a stack deploy, the deploy will update for all the differences. The --resolve-image prevents the image digest resolution, turning latest into sha256:a12341.... But if an old latest is already pulled locally, sounds like it won't update that and you'd need to run a pull again.
|
|
| Apr 6, 2020 at 13:28 | comment | added | Cocowalla |
--resolve-image does pull the latest version - but only when doing docker stack deploy or docker service update; it doesn't do it when the system reboots. After wasting too much time on this, I actually just gave up, disabling the restart_policy and writing a systemd service to manage lifetime instead - this works great, as it calls docker stack rm and then docker stack deploy`. Annoying it wouldn't work with Swarm along tho
|
|
| Apr 6, 2020 at 9:59 | history | answered | BMitch | CC BY-SA 4.0 |