Skip to content

Reasons that can't use runc-dmz #4158

@lifubang

Description

@lifubang

When we were introducing dmz to runc, we have realized that there were 3 reasons we should disable runc-dmz:

  1. runc-dmz does not play well with selinux #4057, fixed by Add selinux-vs-dmz test case and a workaround #4053.
  2. The container process has a CAP_SYS_PTRACE ability, fixed by nsexec: cloned binary rework #3987.
  3. If the container process is not root and the capabilities are not in the ambient set #4125, will be fixed by dmz: don't use runc-dmz in complicated capability setups #4137.

Maybe there are some more scenarios that can't use runc-dmz, please provide to help us improve or deprecate it. Thanks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions