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:
atomic command can't mount/unmount when the docker daemon isn't running, whatever the storage backend is ostree or not.
Version-Release number of selected component (if applicable):
[root@dhcp-2-50 ~]# rpm -q atomic docker skopeo
atomic-1.17.1-1.gitf304570.el7.x86_64
docker-1.12.6-19.git92b10e4.el7.x86_64
skopeo-0.1.19-1.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1. atomic pull busybox --storage ostree
2. systemctl stop docker
3. atomic mount busybox /mnt
Actual results:
[root@hp-dl360g9-04 ~]# atomic pull busybox --storage ostree
Pulling layer 7520415ce76232cdd62ecc345cea5ea44f5b6b144dc62351f2cd2b08382532a3
[root@hp-dl360g9-04 ~]# atomic images list
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE TYPE
busybox latest 32f093055929 2017-05-04 11:36 ostree
[root@hp-dl360g9-04 ~]# systemctl stop docker
[root@hp-dl360g9-04 ~]# atomic images list
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE TYPE
busybox latest 32f093055929 2017-05-04 11:36 ostree
[root@hp-dl360g9-04 ~]# atomic mount busybox /mnt
The docker daemon does not appear to be running.
Expected results:
atomic mount/umount shouldn't depend on docker daemon when the storage backend is ostree
Additional info:
https://trello.com/c/K8QujNBk/93-5-atomic-mount-umount-without-docker-daemon
(In reply to Brent Baude from comment #2)
> Merged https://github.com/projectatomic/atomic/pull/998
This patch works well for me.
[root@dhcp-2-50 atomic]# mkdir -p /mnt/foo/bar
[root@dhcp-2-50 atomic]# systemctl is-active docker
inactive
[root@dhcp-2-50 atomic]# ./atomic mount busybox /mnt/foo
The destination path is not empty.
[root@dhcp-2-50 atomic]# echo $?
1
[root@dhcp-2-50 atomic]# ./atomic --debug mount busybox /mnt/foo/bar
mount -t overlay overlay -olowerdir=/var/lib/containers/atomic/.storage/7520415ce76232cdd62ecc345cea5ea44f5b6b144dc62351f2cd2b08382532a3 /mnt/foo/bar
mount: wrong fs type, bad option, bad superblock on overlay,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
Extracting to /mnt/foo/bar
[root@dhcp-2-50 atomic]# ls /mnt/foo/bar
bin dev etc home root tmp usr var
[root@dhcp-2-50 atomic]# mount | grep foo
/dev/mapper/rhel-root on /mnt/foo/bar type xfs (rw,relatime,seclabel,attr2,inode64,noquota)
[root@dhcp-2-50 atomic]# ./atomic --debug umount /mnt/foo/bar
[root@dhcp-2-50 atomic]# echo $?
0
[root@dhcp-2-50 atomic]# mount | grep foo
[root@dhcp-2-50 atomic]#
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.
https://access.redhat.com/errata/RHBA-2017:1323