RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

I believe this is fixed in docker-1.1-2

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

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