'docker pull' when running 'docker stack deploy' ?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
@marcbihlmaier commented on Thu Sep 28 2017
File: engine/reference/commandline/stack_deploy.md, CC @mstanleyjones
it is not defined here if
docker stack deploy
also pulls the new images, especially if they are tagged again with latest
It would be great to have this documented clearly - especially for people coming from docker-compose, where they are used to run docker-compose pull .
// edited:
seems like it is pulled only when another tag is defined - an the image does not exist locally:
https://github.com/moby/moby/issues/30951
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with engine/reference/commandline/stack_deploy.md and review the linked moby/moby issue 30951 for the observed image-pull behavior. Document clearly when docker stack deploy pulls images, including the latest-tag and locally absent-image cases, and contrast this with the docker-compose pull workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100