KhronosGroup / KhronosGroup/DockerContainers
Purge old containers from dockerhub?
- Dominant language
- Dockerfile
- Stars
- 12
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
There are 10s of GB, possibly in excess of 100 GB, of old containers on Dockerhub that have not been accessed in a long time. Layer caching probably reduces the total but even so, it seems extreme. How would people feel about deleting containers that have not been pulled in, say, 1+ years? Conceivably that will break a build for someone doing archaeology down the line but I see no other drawbacks. Ping @rpavlik @KhronosWebservices as khronosgroup members on dockerhub (I would also ping Lorenzo but I do not know their github handle).
https://hub.docker.com/repository/docker/khronosgroup/docker-images/image-management?sortField=last_pulled&sortOrder=asc
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked Docker Hub image-management page and review the oldest containers by last-pulled date. The issue does not name repository files or tests; clarify the retention rule, affected images, and ownership with the mentioned Khronos maintainers before treating the cleanup as complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100