Skip to content
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

[FEAT]: Container Images Management #272

Open
mandopatriot opened this issue Jul 2, 2024 · 7 comments
Open

[FEAT]: Container Images Management #272

mandopatriot opened this issue Jul 2, 2024 · 7 comments

Comments

@mandopatriot
Copy link

Feature Description

Similar to Containers, Volumes, and Networks, there should be an Images tab under ServApps for listing and management of images. Also, there should be an option to periodically or by selection to clean images that are no longer used - if containers are set to auto update, the old images are not pruned without going into the host and manually doing it.

@azukaar
Copy link
Owner

azukaar commented Jul 3, 2024

FYI Images are periodically pruned already

@mandopatriot
Copy link
Author

Thanks, I that something Cosmos does? What are the details for time, etc?

@azukaar
Copy link
Owner

azukaar commented Jul 3, 2024

Yes, it's every night, can be disabled in the setting page

@mandopatriot
Copy link
Author

I don't know if it is working properly. When I run docker images, I see old images for containers that I've removed from Cosmos. I even tested that after your original reply. Also, running docker image prune shows a good number of images that can be pruned, more than any that may have auto updated. Finally, running docker image prune -a gets rid of any image not connected to a container, which at this run saved around 6GB.

Anyway, having these options and details in Cosmos would be nice, even if it does some of it automatically.

@azukaar
Copy link
Owner

azukaar commented Jul 6, 2024

You can see in the logs, you should either have

"Error pruning images"

or

"Pruned images: "

appearing in them

@mandopatriot
Copy link
Author

You can see in the logs, you should either have

"Error pruning images"

or

"Pruned images: "

appearing in them

It shows as pruning images but I just confirmed that not all images were pruned. After your comment I installed two different containers from the Market, then deleted them. Just now I ran docker image prune -an and it found the leftover images from the containers I deleted. So it’s been 2 days and neither auto run cleaned them. I understand not all auto tasks may or should be as impactful as docker image prune -a, which is why I suggested a page similar to Networks and Volumes, where we can manage them without going into the host directly.

@azukaar
Copy link
Owner

azukaar commented Jul 9, 2024

Hmm it might just be a bug to be honest, I will investigate, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants