Bug 1220303 - Turn on virt_use_nfs boolean on Atomic
Summary: Turn on virt_use_nfs boolean on Atomic
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: ostree
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Giuseppe Scrivano
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-11 09:29 UTC by Jan Safranek
Modified: 2015-12-17 11:31 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-12-17 11:31:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jan Safranek 2015-05-11 09:29:26 UTC
Atomic is supposed just to run containers. In order to allow the containers to read stuff from NFS shares, virt_use_nfs boolean must be enabled manually.

Wouldn't it make more sense to turn it on by default? IMO NFS is/will be pretty widely used to access some shared data between containers.


Version-Release number of selected component (if applicable):
selinux-policy-targeted-3.13.1-122.fc22.noarch



On related note, this dontaudit rule makes debugging of NFS problems really hard, there is no visible AVC when a container reads from a NFS share:

dontaudit svirt_sandbox_domain mountpoint : dir { ioctl read
getattr lock search open } ;

I'm for removing the rule.

Comment 1 Daniel Walsh 2015-05-11 13:48:00 UTC
This is something we would need on project atomic not on the selinux-policy package.

Comment 2 Fedora End Of Life 2015-05-29 13:49:46 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Daniel Walsh 2015-05-29 14:11:47 UTC
Colin is there a bugzilla for the fedora atomic platform?

Comment 4 Colin Walters 2015-12-16 14:37:13 UTC
Pretty sure right now kubernetes-ansible and openshift/ansible are setting this.  And didn't we change the Docker package?

Comment 5 Giuseppe Scrivano 2015-12-17 11:31:46 UTC
this is already done by the Docker package:

commit 9520a0c4a52427ab7338e997479f84060f330e9c
Author: Lokesh Mandvekar <lsm5>
Date:   Thu Jul 30 16:13:35 2015 +0000

    add commit#f12e6c1 from docker-selinux upstream
    
    Turn on virt booleans for use with docker
    
    I think we should default to virt_use_nfs to handle clustered
    situations where selinux blocks nfs volumes.  This makes docker
    containers a little less secure, but improves usability.
    
    Secondly we need to turn on virt_sandbox_use_all_caps to allod
    docker run --cap-add to actually work.  Having SELinux break this
    out of the box kind of stinks.  This gives slightly less security
    since the kernel already controls the capabilities separately.
    
    From: Daniel J Walsh <dwalsh>
    
    Signed-off-by: Lokesh Mandvekar <lsm5>


This is what I have on my Fedora 23 Atomic Host:

bash-4.3# getsebool -a | grep virt_use_nfs
virt_use_nfs --> on

So I am going to close this bug.


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