Add support to containerRunOptions for --cap-drop #389
Comments
ddl-ebrown
added a commit
to ddl-ebrown/container-structure-test
that referenced
this issue
Oct 24, 2023
ddl-ebrown
added a commit
to ddl-ebrown/container-structure-test
that referenced
this issue
Oct 24, 2023
- Support for --cap-add was added as part of GoogleContainerTools#327 - This rounds out the feature set to also include support for --cap-drop - Updates tests to drop "chown" capability and verify doing so works - closes GoogleContainerTools#389
ddl-ebrown
added a commit
to ddl-ebrown/container-structure-test
that referenced
this issue
Feb 29, 2024
- Support for --cap-add was added as part of GoogleContainerTools#327 - This rounds out the feature set to also include support for --cap-drop - Updates tests to drop "chown" capability and verify doing so works - closes GoogleContainerTools#389
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For security reasons, it's often desirable to drop all linux capabilities when running containers in Kubernetes. However, there is currently only a way to add capabilities for tests and no way to drop them.
As seen in, #327, support was only added for
--cap-add--cap-dropcan similarly remove default capabilities - see https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilitiesThe text was updated successfully, but these errors were encountered: