Bug 1326450

Summary:	some network related files are written to /var/lib/docker even if using the daemon's -g option
Product:	Red Hat Enterprise Linux 7	Reporter:	Qian Cai <qcai>
Component:	docker-latest	Assignee:	Antonio Murdaca <amurdaca>
Status:	CLOSED NOTABUG	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	dwalsh
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-06-03 20:56:34 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-12 17:25:28 UTC

Description of problem:
Open upstream as well,
https://github.com/docker/docker/issues/18508

For example, started docker-latest will create files like this,
/var/lib/docker/network/files/8168e8f177c081e70a186211d97a035c869d027fe675da0c0223d299ee5edbcc.sock

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

How reproducible:
always

Comment 1 Qian Cai 2016-04-12 17:27:32 UTC

Looks like this patch needs to be merged first,
https://github.com/docker/libnetwork/pull/742

Comment 3 Daniel Walsh 2016-06-03 20:39:29 UTC

Need this back ported to docker-1.10

Comment 4 Antonio Murdaca 2016-06-03 20:52:25 UTC

There's no patch to be backported unfortunately - the associated PR has been closed https://github.com/docker/libnetwork/pull/742

Comment 5 Antonio Murdaca 2016-06-03 20:54:07 UTC

also, I'd say we can close this also as not a bug because it's not documented anywhere where files for libnetwork goes - and it doesn't change anything, does it?