Bug 1328270

Summary:	may need to use /run/docker-latest/
Product:	Red Hat Enterprise Linux 7	Reporter:	Qian Cai <qcai>
Component:	docker-latest	Assignee:	Lokesh Mandvekar <lsm5>
Status:	CLOSED NOTABUG	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.2	CC:	amurdaca, dwalsh, mpatel
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-03 15:15:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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 .