container/podman
container/podman
1
0
Fork 0
mirror of https://github.com/containers/podman synced 2024-10-20 17:23:30 +00:00
Code Issues Packages Projects Releases Wiki Activity
podman/contrib/imgprune
History
Chris Evich e8564dc44f
Cirrus: Print images that should be pruned 
Over time unless they're removed, the project could grow quite a large
collection of VM images.  While generally cheap (less than a penny each,
per month), these will become a significant cost item if not kept
in-check.

Add a specialized container for handling image-pruning, but limit
it to only finding and printing (not actually deleting) images.

Also update the image-building workflow so that base-images used to
compose cache-images are also labeled with metadata.

N/B: As an additional safeguard, the service account which
     executes the new container in production *DOES NOT*
     have access to delete images.  This can be enabled
     by adding the GCE IAM role: CustomComputeImagePrune

Signed-off-by: Chris Evich <cevich@redhat.com>
2019-07-15 15:26:26 -04:00
..
Dockerfile Cirrus: Print images that should be pruned 2019-07-15 15:26:26 -04:00
entrypoint.sh Cirrus: Print images that should be pruned 2019-07-15 15:26:26 -04:00
README.md Cirrus: Print images that should be pruned 2019-07-15 15:26:26 -04:00

README.md

PODMAN logo

A container image for maintaining the collection of VM images used by CI/CD on this project and several others. Acts upon metadata maintained by the imgts container.

Example build (from repository root):

sudo podman build -t $IMAGE_NAME -f contrib/imgprune/Dockerfile .