We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Thank you for your work on this. It's pretty much the basis for any and every Alpine Linux container image that requires glibc :)
Would it be possible to get the resulting artifacts/packages signed in any way? What I usually see in a lot of Dockerfiles is
apk add --allow-untrusted <some-apk>
That really doesn't fit with my understanding of chain of trust, especially when it comes to something as vital as a C runtime library.
The text was updated successfully, but these errors were encountered:
Sorry, ment to post here.
Sorry, something went wrong.
No branches or pull requests
Thank you for your work on this. It's pretty much the basis for any and every Alpine Linux container image that requires glibc :)
Would it be possible to get the resulting artifacts/packages signed in any way? What I usually see in a lot of Dockerfiles is
That really doesn't fit with my understanding of chain of trust, especially when it comes to something as vital as a C runtime library.
The text was updated successfully, but these errors were encountered: