-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Prevent Docker build environments from creating root-owned artifacts #3354
Conversation
/test pull-kops-e2e-kubernetes-aws |
/test pull-kops-e2e-kubernetes-aws |
/test pull-kops-e2e-kubernetes-aws |
1 similar comment
/test pull-kops-e2e-kubernetes-aws |
/approve |
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.
Thanks
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alrs, chrislovecnm The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/test all [submit-queue is verifying that this PR is safe to merge] |
All the polish you add is seriously appreciated!!!!! |
Automatic merge from submit-queue |
The binaries in
.build/artifacts
are built in Docker containers and are owned by the root user.I've created HOST_UID and HOST_GID variables in the Makefile that are passed in to the Docker build containers so that artifacts can be chowned to the proper user and group IDs.
Previously, it was impossible to
make clean
orrm -rf .build
without root privileges.