mirror of
https://github.com/containers/podman
synced 2024-10-20 17:23:30 +00:00
e8564dc44f
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>
21 lines
621 B
Docker
21 lines
621 B
Docker
FROM centos:7
|
|
|
|
# Only needed for installing build-time dependencies
|
|
COPY /contrib/imgts/google-cloud-sdk.repo /etc/yum.repos.d/google-cloud-sdk.repo
|
|
RUN yum -y update && \
|
|
yum -y install epel-release && \
|
|
yum -y install google-cloud-sdk && \
|
|
yum clean all
|
|
|
|
ENV GCPJSON="__unknown__" \
|
|
GCPNAME="__unknown__" \
|
|
GCPPROJECT="__unknown__" \
|
|
IMGNAMES="__unknown__" \
|
|
BUILDID="__unknown__" \
|
|
REPOREF="__unknown__"
|
|
|
|
COPY ["/contrib/imgts/entrypoint.sh", "/contrib/imgts/lib_entrypoint.sh", "/usr/local/bin/"]
|
|
RUN chmod 755 /usr/local/bin/entrypoint.sh
|
|
|
|
ENTRYPOINT ["/usr/local/bin/entrypoint.sh"]
|