create_service: ensure latest image is used
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 13d 8h
- Merged PRs (30d)
- 2
Description
I have a Docker Swarm running over multiple host machines. I noticed when creating a new service through create_service, it will not always use the latest version of a tagged image, but sometimes use an older, probably on the host machine cached version of the tagged image, instead of the newer image with the same tag on the registry.
I expected it would be default behaviour for the Swarm to always check for the latest version on the registry
Is there a way to ensure the service will always use the latest version of the Docker image?
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 at the create_service entry point and trace how the tagged image is passed to the Docker Engine API for Swarm services. Reproduce the behavior with an image cached on a host and a newer image on the registry, then determine whether image selection belongs in this library or Docker Engine. Done means the expected behavior and any required change are clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100