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: use Google managed base images #2159

Merged
merged 1 commit into from
Mar 26, 2024
Merged

feat: use Google managed base images #2159

merged 1 commit into from
Mar 26, 2024

Conversation

enocom
Copy link
Member

@enocom enocom commented Mar 25, 2024

This commit updates the Bullseye and Buster containers to pull from a Google-managed Debian image.

Context:

Google maintains base images for building its own applications. These images are built from the same source that Docker Hub uses. Therefore, they match the images you would get from Docker Hub.

The advantage of using Google-maintained images is that they are stored on Google Cloud, so you can pull these images directly from your environment without having to traverse networks.

Google updates these images whenever a new version of an official image is released and the new version fixes a known vulnerability reported by Artifact Analysis. For more information on image versions, see the GitHub repository of official images.

See https://cloud.google.com/software-supply-chain-security/docs/base-images

@enocom enocom requested a review from a team as a code owner March 25, 2024 22:11
This commit updates the Bullseye and Buster containers to pull from a
Google-managed Debian image.

Context:

Google maintains base images for building its own applications. These
images are built from the same source that Docker Hub uses. Therefore,
they match the images you would get from Docker Hub.

The advantage of using Google-maintained images is that they are stored
on Google Cloud, so you can pull these images directly from your
environment without having to traverse networks.

Google updates these images whenever a new version of an official image
is released and the new version fixes a known vulnerability reported by
Artifact Analysis. For more information on image versions, see the
GitHub repository of official images.

See https://cloud.google.com/software-supply-chain-security/docs/base-images
@enocom enocom force-pushed the managed-containers branch from 5bf5ed3 to d3d9c7c Compare March 25, 2024 22:12
enocom added a commit to GoogleCloudPlatform/alloydb-auth-proxy that referenced this pull request Mar 25, 2024
Copy link
Collaborator

@jackwotherspoon jackwotherspoon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@enocom enocom merged commit 1103a95 into main Mar 26, 2024
12 checks passed
@enocom enocom deleted the managed-containers branch March 26, 2024 16:10
enocom added a commit to GoogleCloudPlatform/alloydb-auth-proxy that referenced this pull request Mar 28, 2024
enocom added a commit that referenced this pull request Apr 1, 2024
enocom added a commit that referenced this pull request Apr 3, 2024
This is a port of #2159
for the v1 branch.
enocom added a commit that referenced this pull request Apr 3, 2024
This is a port of #2159
for the v1 branch.
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

Successfully merging this pull request may close these issues.

2 participants