Comment on Get notified on Mastodon for new Github releases
Link@rentadrunk.org 11 months agoYou don’t need to run docker-compose down.
docker-compose pull; docker-compose up -d is enough
Comment on Get notified on Mastodon for new Github releases
Link@rentadrunk.org 11 months agoYou don’t need to run docker-compose down.
docker-compose pull; docker-compose up -d is enough
eskuero@lemmy.fromshado.ws 11 months ago
I guess that’s fair for single service composes but I don’t really trust composes with multiple services to gracefully handle only recreating one of the containers
Link@rentadrunk.org 11 months ago
If only one container has been updated then when you run docker compose up -d it will only recreate that container, unless it is a dependency of another container (like a database) in which case it will restart all containers that depend on it as well.
7Sea_Sailor@lemmy.dbzer0.com 11 months ago
You can
docker compose up -d <service>to (re)create only one service from your Dockerfile