Bug 1328270 - may need to use /run/docker-latest/
Summary: may need to use /run/docker-latest/
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker-latest
Version: 7.2
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Lokesh Mandvekar
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-18 21:02 UTC by Qian Cai
Modified: 2016-05-03 17:32 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-03 15:15:12 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Qian Cai 2016-04-18 21:02:20 UTC 
Description of problem:
Right now, everything goes to /run/docker/. The easy part to fix this is to pass --exec-root /run/docker-latest to the docker-latest unit file. The hard part is that netns seems hard-cored and does not honor --exec-root.

# mount
...
proc on /run/docker/netns/8d54a73b0709 type proc (rw,nosuid,nodev,noexec,relatime)

This might be one of reasons caused bug 1328204 . Once this is fixed, we can test to see if that will solve the mentioned bug.

Version-Release number of selected component (if applicable):
docker-latest-1.10.3-9.el7.x86_64

How reproducible:
always
Comment 2 Daniel Walsh 2016-05-03 15:15:12 UTC 
We don't want to support two versions of docker at the same time, since /run/docker.sock is built into two many tools, I don't think we should do this.
Comment 3 Qian Cai 2016-05-03 17:32:16 UTC 
As far as I can tell, docker.sock is always hard-coded in /run/docker/ and does NOT honor --exec-root .
Note You need to log in before you can comment on or make changes to this bug.