mirror of
https://github.com/containers/podman.git
synced 2025-09-22 20:56:21 +08:00
Merge pull request #4806 from vrothberg/seccomp
policy for seccomp-profile selection
This commit is contained in:
@ -676,6 +676,12 @@ If specified, the first argument refers to an exploded container on the file sys
|
||||
This is useful to run a container without requiring any image management, the rootfs
|
||||
of the container is assumed to be managed externally.
|
||||
|
||||
**--seccomp-policy**=*policy*
|
||||
|
||||
Specify the policy to select the seccomp profile. If set to *image*, Podman will look for a "io.podman.seccomp.profile" annotation in the container image and use its value as a seccomp profile. Otherwise, Podman will follow the *default* policy by applying the default profile unless specified otherwise via *--security-opt seccomp* as described below.
|
||||
|
||||
Note that this feature is experimental and may change in the future.
|
||||
|
||||
**--security-opt**=*option*
|
||||
|
||||
Security Options
|
||||
|
@ -697,6 +697,12 @@ of the container is assumed to be managed externally.
|
||||
Note: On `SELinux` systems, the rootfs needs the correct label, which is by default
|
||||
`unconfined_u:object_r:container_file_t`.
|
||||
|
||||
**--seccomp-policy**=*policy*
|
||||
|
||||
Specify the policy to select the seccomp profile. If set to *image*, Podman will look for a "io.podman.seccomp.profile" annotation in the container image and use its value as a seccomp profile. Otherwise, Podman will follow the *default* policy by applying the default profile unless specified otherwise via *--security-opt seccomp* as described below.
|
||||
|
||||
Note that this feature is experimental and may change in the future.
|
||||
|
||||
**--security-opt**=*option*
|
||||
|
||||
Security Options
|
||||
|
Reference in New Issue
Block a user