4 ms·
Nitpicking: Why pull separately? it will pull if no image stored locally or even if the `docker-compose.yml` changed.
by yonixw 6y ago
Nitpicking: Why pull separately? it will pull if no image stored locally or even if the `docker-compose.yml` changed.
- randallsquared 6y agoTwo reasons I've done this in my own Makefiles: predictable start times, and separation of failure-prone steps.
- yjftsjthsd-h 6y agoStale images can be a reason. If I specify `image: foo:latest`, then push new versions, it won't automatically pull new versions unless you do an explicit pull.