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.

Document URL: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html/managing_containers/managing_storage_with_docker_formatted_containers#overlay_graph_driver

Section Number and Name: 1.6. Overlay Graph Driver

Describe the issue:

There are a few variables unexplained in the documentation regarding overlay2 support for docker.
It seems overlay2 support is different than multipath, so if you specify the CONTAINER_ROOT_LV_NAME and CONTAINER_ROOT_LV_MOUNT_PATH variables, it will create a new logical volume for storing container images and container rootfs, otherwise, no new logical volume will be created and overlay2 will be setup on rootfs.

Suggestions for improvement: 
Include proper documentation about how this works and different scenarios, as it is assumed it works like multipath (it will create the lv, etc. without needed those variables)

Additional information: 
There is a related Bugzilla where you can find more information https://bugzilla.redhat.com/show_bug.cgi?id=1490910