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:
Docker thinpools are not recommended upstream by Docker, and operationally it is not possible to get key information about thinpool status - for instance, the usage within the thinpool for a specific container. Docker thinpools are easy to fill (and tracking usage is hard) and recovering from a full thinpool is incredibly difficult.
overlayfs seems to be the best supported storage backend available from the upstream community, but I can find no documentation that suggests that this is supported for RHEL (and I've heard you don't include overlayfs2 in your kernel). Please support the overlayfs storage driver as a storage backend for Docker.
To see this go horribly wrong:
docker start <an-image> -it dd if=/dev/random of=/bigfile
... and wait. In the meantime, try and work out how much of the thinpool the container in question is taking up.
We are working on overlay. overlay2 is fully supported, this has nothing to do with the kernel. Overlay and SELinux do not currently work together, although this has been fixed in upstream kernels. And we will definitely have this fixed in the RHEL kernel, by RHEL7.4 if not sooner.
You can run with overlay and ovleray2 in docker-1.12 release on RHEL, but you have to turn off SELinux, in docker daemon, until the kernel is fixed. (Obviously something I am not crazy about advising)
Overlay is also not Posix Compliant, so we are concerned about certain workloads not working correctly. There are several fixes/issues in the kernel to fix a few of these.
We have a proposal to change the default in Fedora 26 to get more play time on this.
Sounds helpful. To be fair, I phrased this wrong - I'm less worried that overlay specifically is the solution you choose and more concerned that the thinpool model is hard to work with. Whatever solution you have that gets me a manageable docker store with upstream support will do nicely.
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:2344