-
Notifications
You must be signed in to change notification settings - Fork 2k
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
docker.cleanup.image of Docker driver doesn't work as expected. #3560
Comments
I tested locally and images were cleaned up after the default 3 minute delay. Going to close for now but if you can provide client logs that show The expected logs would be something like:
|
here is the log. I've two nomad clients and one of them is cleaning the old images and I can see the logs you mentioned above, but on this one I can't see the removed report. |
@weslleycamilo Is it specific to when your restart Nomad/Docker? |
I am not restarting them, just the job as my testing with Nomad. So I've been restarting the job, stopped it , started it and so on. |
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
0.7.1
Operating system and Environment details
Ubuntu 16.10
Issue
Docker cleanup doesn't work as it is mentioned on the documentation https://www.nomadproject.io/docs/drivers/docker.html
It says it is default to true to cleanup the images but it doesn't clean even if I set it to true.
Reproduction steps
I did set it to true.
and I still got the same images.
Nomad Server logs (if appropriate)
CGroup: /system.slice/nomad-server.service
└─5982 /usr/local/bin/nomad agent --config server.hcl
Nomad Client logs (if appropriate)
The text was updated successfully, but these errors were encountered: