| ▲ | dijit 6 hours ago |
| > I use Docker compose to recreate containers with a new image regularly. try doing so without the compose file though. |
|
| ▲ | bikezen 5 hours ago | parent | next [-] |
| With podman its just `podman auto-update` Will pull the latest version of the image down. |
|
| ▲ | doubled112 6 hours ago | parent | prev | next [-] |
| That's true, isn't it? It was one of those features you'd think they would have had figured out, but no. |
| |
| ▲ | danudey 5 hours ago | parent | next [-] | | The idea is that your container image is the thing you want, and is (relatively) immutable, so you delete and create containers when you want things to change. If you need state you can do that with volume mounts, but the idea is that you don't need to 'update' a container, you just replace it with a new one. That's also what docker compose does, under the hood. It doesn't 'update' a container, it just deletes it and recreates it with the new image and the same settings/name/ports/volumes/etc. | |
| ▲ | prmoustache 6 hours ago | parent | prev [-] | | Isn't the ability to do blue/green deployments, canary releases and easy rollbacks huge incentives to use containers? I think virtually nobody cares about being able to change the image of a container when you can so easily start a new one. | | |
|
|
| ▲ | kcb 5 hours ago | parent | prev [-] |
| Not too hard. The original run command is stored if you inspect a running container. |
