Nitpicking: Why pull separately? it will pull if no image stored locally or even... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		yonixw on June 25, 2020 \| parent \| context \| favorite \| on: Show HN: Aviary.sh – A tiny Bash alternative to An... Nitpicking: Why pull separately? it will pull if no image stored locally or even if the `docker-compose.yml` changed.

yjftsjthsd-h on June 25, 2020 | [–]

Stale 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.

randallsquared on June 25, 2020 | [–]

Two reasons I've done this in my own Makefiles: predictable start times, and separation of failure-prone steps.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact