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.
This will be fixed in RHEL7.4.
As overlay/overlay2 is supported with selinux in docker-1.12.6-48.git0fdc778.el7.x86_64, move to verified.
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.