Bug 1125108

Summary:	Stopping docker service unmounts btrfs filesystem
Product:	Red Hat Enterprise Linux 7	Reporter:	Avi Miller <avi.miller>
Component:	docker	Assignee:	Daniel Walsh <dwalsh>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	alexl, avi.miller, bsarathy, lsm5, lsu, mjenner, sghosh
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:	2014-09-18 20:46:35 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:
Embargoed:
Bug Depends On:	1128041
Bug Blocks:	1109938

Description Avi Miller 2014-07-31 04:34:22 UTC

Description of problem:

If you put /var/lib/docker on a btrfs filesystem, Docker switches to using the btrfs storage engine. However, if you stop the docker service, it unmounts /var/lib/docker which means if you start it again, the btrfs filesystem is gone and it switches to using device-mapper on the wrong filesystem.

Version-Release number of selected component (if applicable):

docker-0.11.1-22.el7

How reproducible:

100%

Steps to Reproduce:
1. Create a btrfs filesystem
2. Mount the btrfs filesystem on /var/lib/docker
3. Start docker
4. Check the storage engine is btrfs via "docker info"
5. Stop docker

Actual results:

btrfs filesystem at /var/lib/docker is unmounted

Expected results:

btrfs filesystem should remain mounted after docker stops.

Additional info:

None.

Comment 2 Daniel Walsh 2014-07-31 13:21:35 UTC

I believe this is fixed in docker-1.1-2

Comment 3 Luwen Su 2014-08-06 10:04:05 UTC

It's okay for me if does it without selinux in docker-1.1.2-6.el7.x86_64, but i still want to keep the bug status as the scenario lack of selinux supporting.
https://github.com/docker/docker/pull/6452/files

Comment 5 errata-xmlrpc 2014-09-18 20:46:35 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1266.html