Skip to content

Conversation

frjaraur
Copy link

I had a problem working on a SElinux enabled environment and I added a quick patch, adding an option and standard SELinux labels allowing containers to manage CIFS volume content (I wasn´t able to read or write any CIFS volume because SELinux does not allow this operations from containers using its default cifs_t label).
If selinuxEnabled: "true" option is used, context=system_u:object_r:container_file_t:s0 will be added as option during mount operation.

…d hosts

Added SElinux as option at is required for mounting on SELinux enabled hosts. I found this issue when I was improving security for our environment.
…use any SElinux feature.

Added an example using selinuxEnabled option. By default it will not use any SElinux feature. I added the following common SELinux labels (from Red Hat best practices with containers):
      selevel: s0
      serole: object_r
      setype: container_file_t
      seuser: system_u

Using container_file_t, containers will be available to manage mount content.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant