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.

Created attachment 939077 [details]
[PATCH] Support /etc/sysconfig/docker-storage

This will allow installation programs to pre-configure storage easily.
It will be used by Atomic to set up Docker for direct LVM.
---
 docker-storage.sysconfig | 14 ++++++++++++++
 docker.service           |  3 ++-
 docker.spec              |  5 ++++-
 3 files changed, 20 insertions(+), 2 deletions(-)
 create mode 100644 docker-storage.sysconfig

The rationale for a separate sysconfig file is that in-place modification of /etc/sysconfig/docker is ugly for Anaconda or the disk image generation scripts to do; we'd have to sed.  That's still possible though, it just feels cleaner to me if we separate what admins edit and what tools generate.

Other options are:

1) Have Docker search for an lvm volumes named docker-data, docker-metadata on startup and automatically use them
2) Something else?

Applied to  docker-1.2.0-17.el7

We need to get this into Centos and Fedora.