Bug 1326450 - some network related files are written to /var/lib/docker even if using the daemon's -g option
Summary: some network related files are written to /var/lib/docker even if using the d...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker-latest
Version: 7.3
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Antonio Murdaca
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-12 17:25 UTC by Qian Cai
Modified: 2016-06-03 20:56 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-03 20:56:34 UTC
Target Upstream Version:

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

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?
Note You need to log in before you can comment on or make changes to this bug.