Description
I use volumes with type=image a lot. offen because to it allows me add static apps to nginx without having a seperate container running another nginx. this works prefectly but I don't have a way to automatically update the used images. I can doing docker pull on each image but i think the purpose of docker compose pull was exactly to do that.
Steps To Reproduce
for example create compose.yaml with this content:
services:
nginx:
image: "nginx:alpine"
volumes:
- type: image
source: mattfly/obsidian:latest
target: /srv/http/ObsidianIRC
image:
subpath: usr/share/nginx/html/
- do
docker compose up and then ctrl-c
- wait untill a new release be pushed to
mattfly/obsidian:latest
- do
docker compose pull
- you expect to new version
mattfly/obsidian:latest be pulled but it does not and doing docker compose up will run container with the old version of mattfly/obsidian:latest
Compose Version
Docker Compose version v5.1.3
Description
I use volumes with
type=imagea lot. offen because to it allows me add static apps tonginxwithout having a seperate container running another nginx. this works prefectly but I don't have a way to automatically update the used images. I can doingdocker pullon each image but i think the purpose ofdocker compose pullwas exactly to do that.Steps To Reproduce
for example create compose.yaml with this content:
docker compose upand then ctrl-cmattfly/obsidian:latestdocker compose pullmattfly/obsidian:latestbe pulled but it does not and doingdocker compose upwill run container with the old version ofmattfly/obsidian:latestCompose Version