Unverified Commit fa19bff7 authored by Jake Howard's avatar Jake Howard Committed by GitHub
Browse files

Update README.md

parent f06d2527
......@@ -17,3 +17,11 @@ If newer containers are available than those running, pull the new containers, a
- If there are images, pull (`docker-compose pull`)
- List images again
- If images list is different, cycle container (`docker-compose down && docker-compose up -d`)
## _"How's this different from `pull` and `up -d`?"_
After writing this, turns out that `docker-compose` support doing most of this for you.
> If there are existing containers for a service, and the service’s configuration or image was changed after the container’s creation, `docker-compose up` picks up the changes by stopping and recreating the containers (preserving mounted volumes).
Therefore, you can easily achieve this by simply pulling each compose file, and running `up -d`. Which changes all this Rust into [a handful of lines of Bash]( https://github.com/RealOrangeOne/infrastructure/blob/master/ansible/roles/docker_cleanup/files/docker-utils/update-all).
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment