-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Nomad force_pull=false
default not working
#11220
Comments
hello, I think your problem may be with docker image garbage collection which happens after a short time.
there are more gc options you can configure, see |
Hi @fluffyf-x , Thx for using Nomad! Can you try out the suggestion @gabrieltz suggested and let us know if that resolves your issue? Thanks! @DerekStrickland and the Nomad Team PS. Thanks @gabrieltz for pitching in! |
hi @gabrieltz & @DerekStrickland : we have gc image collection set to false
I'll add the image_delay thank you both! |
Hi @fluffyf-x , I'm going to go ahead and close this issue, but feel free to re-open if you still feel there's a bug.
|
Thank you for the prompt response |
Can you check with the latest nomad version? Nomad 1.0.0 had a bug fix related to image cleanup/GCing in #9101 . Prior to the fix, the image will be GCed immediately on failure, and it will be pulled on next restart. @gabrieltz suggestion works around this bug. I'm commenting here, to avoid polluting issue #11240 with image force_pull details. It seems independent from the memory leak. Thanks! |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
Output from
nomad version
Nomad v0.12.7 (6147cb578794cb2d0c35d68fe1791728a09bb081)
Operating system and Environment details
running docker with nomad
Issue
We've seen in production that nomad pulls containers everytime a job restarts, however the documentation states that force_pull is set to false by default
Reproduction steps
kill a container to force a nomad restart
Expected Result
nomad pulls local images before fetching from remote
Actual Result
nomad pulls an image everytime
Job file (if appropriate)
Nomad Server logs (if appropriate)
Nomad Client logs (if appropriate)
The text was updated successfully, but these errors were encountered: