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.
DescriptionWelterlen Benoit
2019-11-20 14:52:38 UTC
Description of problem:
If docker is running but has no Docker Root Dir defined, all FS will be ignored during rear mkbackup.
Version-Release number of selected component (if applicable):
rear-2.4-9.el7_7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. run docker without Docker Root Dir
2. run rear mkbackup
3.
Actual results:
All FS excluded:
Expected results:
FS other than docker included and backup completes.
Additional info:
This is due to the check in 230_filesystem_layout.sh that tries to avoid docker FS:
---
# docker specific exclude part
if is_true $docker_is_running ; then
# docker daemon/service is running
docker_root_dir=$( docker info 2>/dev/null | grep 'Docker Root Dir' | awk '{print $4}' )
# If $docker_root_dir is in the beginning of the $mountpoint string then FS is under docker control
# and we better exclude from saving the layout,
# see https://github.com/rear/rear/issues/1749
Log "$device is mounted below $docker_root_dir (mount point $mountpoint is under docker control), skipping."
echo "$mountpoint" | grep -q "^$docker_root_dir" && continue
fi
---
=> It is based on the output of "docker info" and greps the entry 'Docker Root Dir'.
Already fixed upstream:
https://github.com/rear/rear/pull/2021
For those not familiar with Docker, what are the steps to install Docker and configure it to have no Docker Root Dir defined, if you have them, please? It will make QA work easier if there is an exact reproducer. Thanks
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-2020:1153
Description of problem: If docker is running but has no Docker Root Dir defined, all FS will be ignored during rear mkbackup. Version-Release number of selected component (if applicable): rear-2.4-9.el7_7.x86_64 How reproducible: Always Steps to Reproduce: 1. run docker without Docker Root Dir 2. run rear mkbackup 3. Actual results: All FS excluded: Expected results: FS other than docker included and backup completes. Additional info: This is due to the check in 230_filesystem_layout.sh that tries to avoid docker FS: --- # docker specific exclude part if is_true $docker_is_running ; then # docker daemon/service is running docker_root_dir=$( docker info 2>/dev/null | grep 'Docker Root Dir' | awk '{print $4}' ) # If $docker_root_dir is in the beginning of the $mountpoint string then FS is under docker control # and we better exclude from saving the layout, # see https://github.com/rear/rear/issues/1749 Log "$device is mounted below $docker_root_dir (mount point $mountpoint is under docker control), skipping." echo "$mountpoint" | grep -q "^$docker_root_dir" && continue fi --- => It is based on the output of "docker info" and greps the entry 'Docker Root Dir'. Already fixed upstream: https://github.com/rear/rear/pull/2021