Red Hat Bugzilla – Bug 1253618
Cannot link containers, cannot mount volumes
Last modified: 2015-08-14 07:04:31 EDT
Description of problem:
This bug is a merge of #1244124, #1253604 and #1234757.
It started happening after last update today, and I cannot mount volumes nor link containers.
Containers can be linked using the known workaround from bug 1244124 comment 35.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. For the linking issue, see bug 1244124 comment 14.
2. For the volume issue:
1. setenforce 1
2. docker run -it --rm --volume /home:/home busybox ls /home
--> ls: can't open '/home': Permission denied
3. setenforce 0
4. docker run -it --rm --volume /home:/home busybox ls /home
--> yajo lost+found
All was working fine with docker-1.7.1-7.gitd5a81b3.fc22.
Writing links to easier reading:
This bug is a merge of bug 1244124, bug 1253604 and bug 1234757.
Would be nice to have comment preview in bugzilla XD
If you volume mount your homedir into a container, you need to run with SELInux turned off and probably --privileged.
SELinux will not let you work on your homedir unless you relabel and relabeling your homedir is probably a bad idea.
This was not working in 1.7 unless your machine was in permissive mode.
OK, after `restorecon -RF /home` and using `--volume` with `:z` at the end, it works. But what about the other problem?
The other problems are marked as closed and confirmed fixed.