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.
DescriptionAntonio Murdaca
2015-12-15 17:45:56 UTC
Description of problem:
After the very first run of the docker daemon with devicemapper as the storage backend, docker info will show an empty string for Backing Filesystem
Version-Release number of selected component (if applicable):
docker-1.10.0-12.gitc3726aa.fc24.x86_64
How reproducible:
Always
Steps to Reproduce:
1. systemctl stop docker
2. rm -rf /var/lib/docker
3. systemctl start docker
4. docker info (shows "xfs")
5. systemctl restart docker
6. docker info (shows "")
Actual results:
docker info shows an empty string for Backing Filesystem after the very first run
Expected results:
docker info always shows Backing Filesystem
Additional info:
None
(In reply to Antonio Murdaca from comment #0)
> 6. docker info (shows "")
>
Antonio, I gave a try on docker-1.9.1-15.el7.x86_64, there is no any value/string is showed in 'Backing Filesystem:' after step 6, just a confirmation, it should be an expected result, right?
# docker info|grep "Backing Filesystem"
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
Backing Filesystem:
(In reply to Alex Jia from comment #4)
> (In reply to Antonio Murdaca from comment #0)
>
> > 6. docker info (shows "")
> >
>
> Antonio, I gave a try on docker-1.9.1-15.el7.x86_64, there is no any
> value/string is showed in 'Backing Filesystem:' after step 6, just a
> confirmation, it should be an expected result, right?
>
> # docker info|grep "Backing Filesystem"
> WARNING: bridge-nf-call-iptables is disabled
> WARNING: bridge-nf-call-ip6tables is disabled
> Backing Filesystem:
This is fxed in docker-1.10 not 1.9
The Backing Filesystem still is xfs after step 5 in Description w/ docker-latest 1.10.3-10 and 1.10.3-19
Ater step 5 in Description.
# docker-latest info|grep xfs
WARNING: Usage of loopback devices is strongly discouraged for production use. Either use `--storage-opt dm.thinpooldev` or use `--storage-opt dm.no_warn_on_loop_devices=true` to suppress this warning.
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
Backing Filesystem: xfs
# docker info|grep xfs
Backing Filesystem: xfs
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
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://rhn.redhat.com/errata/RHEA-2016-1057.html