-
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 memory leak and pulling images with force_pull set to false #11240
Comments
Thanks for the report @fluffyf-x. Would you be able to test with a 1.x version of Nomad to see if the problem still persists? |
@lgfa29 : we were not able to test with the newer version, is there any chance you have the PR for the fix? |
Hi @fluffyf-x Nomad 1.2.4 included a fix for a goroutine leak which you can see in #11741. Nomad 0.12.7 is long out of support, so we strongly recommend upgrading to get security fixes. If you still see a leak on Nomad 1.2.4 or above, please let us know. |
Thank you @tgross @Igfa22, we upgraded to 1.0.0 and will upgrade to 1.2.4 today and let you know. I will close this issue in a week with a conclusion if we no longer see the memory leak. |
Closing issue as resolved, thank you team! |
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
Issue
Nomad has a memory leak which we created a cron job to
systemctl restart nomad
every week, is there a fix for the memory leakNomad force_pull according to docs is false by default, however we see errors from pulling images on restart.
prev issue: Nomad
force_pull=false
default not working #11220Reproduction steps
Expected Result
Actual Result
Job file (if appropriate)
Nomad Server logs (if appropriate)
Nomad Client logs (if appropriate)
The text was updated successfully, but these errors were encountered: