Bug 1369159 - label /var/lib/kubelet svirt_sandbox_file_t
Summary: label /var/lib/kubelet svirt_sandbox_file_t
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.3
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Lukas Vrabec
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks: 1369168
TreeView+ depends on / blocked
 
Reported: 2016-08-22 14:38 UTC by Eric Paris
Modified: 2019-12-16 06:26 UTC (History)
13 users (show)

Fixed In Version: selinux-policy-3.13.1-95.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1369168 (view as bug list)
Environment:
Last Closed: 2016-11-04 02:37:33 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2283 0 normal SHIPPED_LIVE selinux-policy bug fix and enhancement update 2016-11-03 13:36:25 UTC

Description Eric Paris 2016-08-22 14:38:12 UTC
We need to have /var/lib/kubelet labeled as svirt_sandbox_file_t because we do container data storage under that location.

Comment 4 Lukas Vrabec 2016-09-07 08:32:47 UTC
Guys, 
Please make deal which label is better and right for /var/lib/kubelet. 

Dan, 
If this solution is wrong, please switch it to ASSIGNED. 

Thanks.

Comment 5 Eric Paris 2016-09-08 02:50:44 UTC
one label works, one label just flat is impossible to use. We go with my way to solve the (many) real customer issues now. pmorie/dwalsh can work this week to look for a better long term solution which is likely to require extensive userspace rewrites. Which take a long time to get upstream. But for now, I know Dan doesn't like it, but sandbox_file_t:s0 on /var/lib/kubelet.

Comment 6 Daniel Walsh 2016-09-08 19:27:33 UTC
Paul Morie and I had a talk on bluejeans, and I believe just changing kubernetes to always specify the :Z will fix the issue.

Comment 8 errata-xmlrpc 2016-11-04 02:37:33 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2283.html


Note You need to log in before you can comment on or make changes to this bug.