diff options
| author | Anhad Jai Singh <ajaisingh@tower-research.com> | 2017-02-10 20:52:55 +0530 |
|---|---|---|
| committer | Brian Coca <bcoca@users.noreply.github.com> | 2017-02-27 09:13:28 -0500 |
| commit | 13dd4b108c82255387bce5c6bd58da48a130642c (patch) | |
| tree | e9487312f3cf30607f62428c18aab71843c0717c /examples/ansible.cfg | |
| parent | 05d719a9f1a5153a45ed979991f97e2cb7f28d8e (diff) | |
| download | ansible-13dd4b108c82255387bce5c6bd58da48a130642c.tar.gz | |
Add 9p to list of special filesystems for selinux
When trying to copy files onto a Virtio-9p filesystem[1][2] int the host
using something like the template module, ansible throws an error that
says something like:
invalid selinux context: [Errno 95] Operation not supported
Adding 9p to the list of exceptional filesystems forces ansible to not
try to set an SELinux context on copied files.
[1] such as one mounted in a qemu VM, using:
# http://www.linux-kvm.org/page/9p_virtio
qemu-kvm [...] -virtfs local,id=apps_dev,path=/host/dir,security_model=passthrough,mount_tag=host_dir
[2] https://www.kernel.org/doc/Documentation/filesystems/9p.txt
Change-Id: Ia868dadce1ffd2b5bebf5ee1804501676e9d7e5f
Diffstat (limited to 'examples/ansible.cfg')
| -rw-r--r-- | examples/ansible.cfg | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/examples/ansible.cfg b/examples/ansible.cfg index 291311ae2b..40126ee91a 100644 --- a/examples/ansible.cfg +++ b/examples/ansible.cfg @@ -372,7 +372,7 @@ # file systems that require special treatment when dealing with security context # the default behaviour that copies the existing context or uses the user default # needs to be changed to use the file system dependent context. -#special_context_filesystems=nfs,vboxsf,fuse,ramfs +#special_context_filesystems=nfs,vboxsf,fuse,ramfs,9p # Set this to yes to allow libvirt_lxc connections to work without SELinux. #libvirt_lxc_noseclabel = yes |