-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update container-selinux.8 man page #311
Conversation
Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
@@ -1476,6 +1476,7 @@ optional_policy(` | |||
unconfined_domain(kubelet_t) | |||
') | |||
|
|||
manage_chr_files_pattern(container_engine_t, fusefs_t, fusefs_t) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this a dup? I see the same line already on 1459
Tests failed. @containers/packit-build please check. |
.PP | ||
.B STANDARD FILE CONTEXT | ||
|
||
SELinux defines the file context types for the container, if you wanted to | ||
store files with these types in a different paths, you need to execute the semanage command to specify alternate labeling and then use restorecon to put the labels on disk. | ||
|
||
.B semanage fcontext -a -t container_ro_file_t '/srv/mycontainer_content(/.*)?' | ||
.B semanage fcontext -a -t container_var_lib_t '/srv/container/content(/.*)?' | ||
.br | ||
.B restorecon -R -v /srv/mycontainer_content |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this also change to /srv/container/content
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes this looks like a bug in the tool used to generate the man page.
ignore centos stream 9 failure. LGTM overall apart from the couple of comments. Suggestion: Maybe we should consider rewriting the manpage in markdown and have go-md2man or other such tool generate the actual manpage at build time ? |
These man pages are autogenerated, based on policy changes and the overall policy on the system. |
No description provided.