-
Notifications
You must be signed in to change notification settings - Fork 619
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
Agent errors and does not clean-up 'dangling' images #2017
Comments
sparrc
added a commit
to sparrc/amazon-ecs-agent
that referenced
this issue
May 7, 2019
sparrc
added a commit
to sparrc/amazon-ecs-agent
that referenced
this issue
May 7, 2019
Use ImageID to cleanup images rather than tag name, to guarantee that we are passing a legitimate identifier to InspectImage and RemoveImage. closes aws#2017
sparrc
added a commit
to sparrc/amazon-ecs-agent
that referenced
this issue
May 7, 2019
Use ImageID to cleanup images rather than tag name, to guarantee that we are passing a legitimate identifier to InspectImage and RemoveImage. closes aws#2017
sparrc
changed the title
Agent does not clean up 'dangling' images
Agent errors and does not clean-up 'dangling' images
May 8, 2019
sparrc
added a commit
to sparrc/amazon-ecs-agent
that referenced
this issue
May 15, 2019
Use ImageID to cleanup images rather than tag name, to guarantee that we are passing a legitimate identifier to InspectImage and RemoveImage. closes aws#2017
sparrc
added a commit
to sparrc/amazon-ecs-agent
that referenced
this issue
May 16, 2019
Use ImageID to cleanup images rather than tag name, to guarantee that we are passing a legitimate identifier to InspectImage and RemoveImage. closes aws#2017
sparrc
added a commit
to sparrc/amazon-ecs-agent
that referenced
this issue
May 21, 2019
Use ImageID to cleanup images rather than tag name, to guarantee that we are passing a legitimate identifier to InspectImage and RemoveImage. closes aws#2017
sparrc
added a commit
to sparrc/amazon-ecs-agent
that referenced
this issue
May 22, 2019
Use ImageID to cleanup images rather than tag name, to guarantee that we are passing a legitimate identifier to InspectImage and RemoveImage. closes aws#2017
sparrc
added a commit
to sparrc/amazon-ecs-agent
that referenced
this issue
May 22, 2019
Use ImageID to cleanup images rather than tag name, to guarantee that we are passing a legitimate identifier to InspectImage and RemoveImage. closes aws#2017
sparrc
added a commit
to sparrc/amazon-ecs-agent
that referenced
this issue
May 22, 2019
Use ImageID to cleanup images rather than tag name, to guarantee that we are passing a legitimate identifier to InspectImage and RemoveImage. closes aws#2017
sparrc
added a commit
to sparrc/amazon-ecs-agent
that referenced
this issue
May 22, 2019
Use ImageID to cleanup images rather than tag name, to guarantee that we are passing a legitimate identifier to InspectImage and RemoveImage. closes aws#2017
sparrc
added a commit
to sparrc/amazon-ecs-agent
that referenced
this issue
May 23, 2019
Use ImageID to cleanup images rather than tag name, to guarantee that we are passing a legitimate identifier to InspectImage and RemoveImage. closes aws#2017
closed by #2023 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
The Agent is not able to cleanup 'dangling' images (
docker images -f dangling=true
). These are image IDs that do not have any tags. They will show up indocker images
with name<none>:<none>
The issue is that the image manager lists all images by name, then attempts to inspect each image based on the name. Dangling images with name
none
throw an error on image inspection and will never get cleaned up.Solution could be to list images by ID, then determine exclusions after inspecting the image.
Supporting Log Snippets
When a customer has a dangling image, they will see error messages like this in the logs:
The text was updated successfully, but these errors were encountered: