mirror of
https://github.com/pelican-dev/panel.git
synced 2026-07-16 04:03:50 +03:00
Automatic cleanup of dangling docker images induced by updated egg containers #55
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @lancepioch on GitHub (May 17, 2024).
Originally assigned to: @parkervcp on GitHub.
Discussed in https://github.com/pelican-dev/panel/discussions/54
Originally posted by DerLev April 13, 2024
I have had some issues in the past with dangling docker images filling up my storage on my wings host. An automatic task for cleaning up those dangling images would be nice. A current workaround is to set a cron job, which works fine but if this was to be included in the daemon itself or just as a simple note in the docs it would greatly help new users setting things up
@rmartinoscar commented on GitHub (May 17, 2024):
Would it run
docker image rm <image id> -for ratherdocker image prune -f?@iamkubi commented on GitHub (May 18, 2024):
I did add a wings endpoint that returns container usage data and allows pruning of images. (https://github.com/pelican-dev/wings/pull/6)
This isn't exposed in the node admin area yet, but it can be in the future. I'll also look into removing an image if it's no longer used after a server is deleted that can be enabled/disabled.
@parkervcp commented on GitHub (May 19, 2024):
prune will remove images that are not being used. If a server is removed any dangling images would be removed by a prune.
@iamkubi commented on GitHub (May 19, 2024):
In my opinion it's better to have the least impact than to prune all images just because one image is no longer in use.
@parkervcp commented on GitHub (May 19, 2024):
prune could be ran every minute and I doubt it would have problems.
@iamkubi commented on GitHub (May 19, 2024):
You could also clear your DNS cache every time you make a DNS query, but why would you?