Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
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 4RHEL 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.
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: