Bug 1253618 - Cannot link containers, cannot mount volumes
Cannot link containers, cannot mount volumes
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: docker (Show other bugs)
22
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Lokesh Mandvekar
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-14 05:25 EDT by Yajo
Modified: 2015-08-14 07:04 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-14 06:37:19 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Yajo 2015-08-14 05:25:35 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):
docker-1.7.1-8.gitb6416b7.fc22.x86_64
docker-fish-completion-1.7.1-8.gitb6416b7.fc22.x86_64
docker-selinux-1.7.1-8.gitb6416b7.fc22.x86_64


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


Additional info:
All was working fine with docker-1.7.1-7.gitd5a81b3.fc22.
Comment 1 Yajo 2015-08-14 05:27:15 EDT
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
Comment 2 Daniel Walsh 2015-08-14 06:37:19 EDT
If you volume mount your homedir into a container, you need to run with SELInux turned off and probably --privileged.

--security-opt label:disabled

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.
Comment 3 Yajo 2015-08-14 07:00:30 EDT
OK, after `restorecon -RF /home` and using `--volume` with `:z` at the end, it works. But what about the other problem?
Comment 4 Daniel Walsh 2015-08-14 07:04:31 EDT
The other problems are marked as closed and confirmed fixed.

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