-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Excessive amount of image pulls #125
Comments
Hm. I suppose we could optimize that by aggregating the used images to eliminate duplicates - but the actual |
What is your top concern?
The former one is due to
For later one, I guess (no proof) |
Run a quick experiment: 2 |
FWIW: See the workaround to use a registry mirror at #73 (comment) |
Registry mirroring is also one thing I did. You may use this as a template to setup your own repo https://github.com/shizunge/dockerhub-mirror |
Im not 100% up to date on this stuff. What exactly would the registry mirroring do and how would it help in my situation? |
essentially pull images from docker registry to your github registry. Then deploy the image from github registry, as github registry doesn't have a stupid rate limit. |
i have 50 containers running. 28 stacks but of course being docker swarm i have some containers replicated.
Shepherd is going through all 200 of my pulls before its able to update them all.
Is there any way to tone this down?? i have multiple stacks that rely on the same image. For example mariadb. but it still tries to pull a new image for every service even if they are running same image.
The text was updated successfully, but these errors were encountered: