Skip to content
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

selinux: use next stream instead of mv workaround #39

Merged
merged 1 commit into from
Oct 27, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 7 additions & 8 deletions selinux/Dockerfile
Original file line number Diff line number Diff line change
@@ -1,9 +1,8 @@
# Change a SELinux boolean. The first line is a workaround for a conflict
# between overlayfs semantics and libselinux that is on track to being fixed, see
# Change a SELinux boolean. The FROM line is using the `next` tag
# as workaround for a conflict between overlayfs semantics and
# libselinux. This issue is already fixed on the `next` CoreOS
# stream but has not reached the stable CoreOS stream.
# https://github.com/SELinuxProject/selinux/pull/342
FROM quay.io/fedora/fedora-coreos:stable
# See above; temporary work around; this should be fixed in newer libselinux. Note
# that this `mv` incantation *must* be in the same RUN line (i.e. same layer) as
# the policy changes.
RUN mv /etc/selinux/targeted/active{,.tmp} && mv /etc/selinux/targeted/active{.tmp,} && \
setsebool -P -N container_manage_cgroup 1
FROM quay.io/fedora/fedora-coreos:next

RUN setsebool -P -N container_manage_cgroup 1