-
Notifications
You must be signed in to change notification settings - Fork 350
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
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
force-pushed
the
managed-containers
branch
from
March 25, 2024 22:12
5bf5ed3
to
d3d9c7c
Compare
enocom
added a commit
to GoogleCloudPlatform/alloydb-auth-proxy
that referenced
this pull request
Mar 25, 2024
jackwotherspoon
approved these changes
Mar 26, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
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 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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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