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

Security review: investigate which container capabilities are truly needed for build #2225

Open
natalieparellano opened this issue Apr 23, 2024 · 0 comments
Labels
help wanted Need some extra hands to get this done.

Comments

@natalieparellano
Copy link
Member

Description

In the security review, this is INFO-2: Excessive Docker container capabilities Build process. The action plan notes that

Docker containers used to build an application are launched with Docker’s default set of capabilities

Proposed solution

We could investigate (by iteratively removing capabilities) which ones are truly needed for the build process to succeed. This MAY differ by phase (e.g., analyze which requires registry/docker socket vs detect/build). We might be able to learn some things from what kpack is doing.

@natalieparellano natalieparellano added the help wanted Need some extra hands to get this done. label May 2, 2024
@natalieparellano natalieparellano transferred this issue from buildpacks/pack-private Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Need some extra hands to get this done.
Projects
None yet
Development

No branches or pull requests

1 participant