- 4,064
- 1,395
- NAS
- DS4l8play, DS202j, DS3623xs+, DSM 7.3.3-25847
I'm curious what approach y'all find best for updating images used by stack deployments.
A brutish method is to delete the docker images, and then redeploy the stack.
Alternately, one can select each container manually, and then "Recreate" with the image pull option selected.
Any thoughts there? Other methods (using Portainer).
And a question for the obsessive/compulsive users here... When I launched a Bookstack stack, the containers appear with a simple Image label... for example, "lscr.io/linuxserver/bookstack:latest". However, if I stop the stack and make any change to the stack compose file (ex. change an external port) when I restart the stack, the individual container's Image name is more cryptic… for example... ".433ed418c483" ... Is that purposeful, or a "bug". If I then stop the stack, delete its images, and redeploy it, the Image name reverts to "lscr.io/linuxserver/bookstack:latest".
Thanks in advance
A brutish method is to delete the docker images, and then redeploy the stack.
Alternately, one can select each container manually, and then "Recreate" with the image pull option selected.
Any thoughts there? Other methods (using Portainer).
And a question for the obsessive/compulsive users here... When I launched a Bookstack stack, the containers appear with a simple Image label... for example, "lscr.io/linuxserver/bookstack:latest". However, if I stop the stack and make any change to the stack compose file (ex. change an external port) when I restart the stack, the individual container's Image name is more cryptic… for example... ".433ed418c483" ... Is that purposeful, or a "bug". If I then stop the stack, delete its images, and redeploy it, the Image name reverts to "lscr.io/linuxserver/bookstack:latest".
Thanks in advance