Skip to content

SELinux super_t label not applied based on manifest seLinuxOptions container config #3156

Answered by bcressey
btiernay asked this question in Q&A
Discussion options

You must be logged in to vote

privileged: true causes the "what label should I use?" logic in containerd-cri to take a different path, which leads to no specific label being set and getting the default domain transition to control_t.

It's almost possible to roll your own privileged: true equivalent (by adding all capabilities, setting a privileged SELinux label, disabling seccomp).

The main privilege that can't be picked up that way is the ability to modify all devices, since there's no field for that in the security context.

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@btiernay
Comment options

@btiernay
Comment options

Answer selected by btiernay
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants