Bug 1400789 - [RFE] Atomic mount is supported on the btrfs docker storage backend
Summary: [RFE] Atomic mount is supported on the btrfs docker storage backend
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: atomic
Version: 7.4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Jindrich Novy
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-02 05:42 UTC by Alex Jia
Modified: 2021-01-15 07:28 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-15 07:28:54 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Alex Jia 2016-12-02 05:42:25 UTC
Description of problem:
At present, Atomic mount is not supported on the btrfs docker storage backend, the result is some atomic commands don't work such as atomic {mount, scan}.

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

# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.3 (Maipo)

# rpm -q atomic docker
atomic-1.13.8-1.el7.x86_64
docker-1.10.3-59.el7.x86_64

# docker info | grep -A1 "Storage Driver"
Storage Driver: btrfs
 Build Version: Btrfs v4.4.1


How reproducible:
always

Steps to Reproduce:
1. docker pull busybox
2. atomic mount busybox /tmp

Actual results:

# docker pull busybox
Using default tag: latest
Trying to pull repository registry.access.redhat.com/busybox ... 
unknown: Not Found
Trying to pull repository docker.io/library/busybox ... 
latest: Pulling from docker.io/library/busybox
56bec22e3559: Pull complete 
Digest: sha256:29f5d56d12684887bdfa50dcd29fc31eea4aaf4ad3bec43daf19026a7ce69912
Status: Downloaded newer image for docker.io/busybox:latest

# atomic mount busybox /tmp
Atomic mount is not supported on the btrfs docker storage backend.

Expected results:


Additional info:

Comment 2 Alex Jia 2017-06-10 04:04:52 UTC
http://www.projectatomic.io/docs/filesystems/

Comment 4 RHEL Program Management 2021-01-15 07:28:54 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


Note You need to log in before you can comment on or make changes to this bug.