The xfs_info utility can be used to verify that ftype=1. NOTE: In modern versions of Centos and RHEL, ftype=1 is the default. As of CentOS/RHEL 7.2, only XFS is currently supported for use as a lower layer file system.įor more a more detailed breakdown of installing docker, see the Docker CE for CentOS installation page. OverlayFS avoids known issues with devicemapper in loop-lvm mode and allows containers to use docker-in-docker, if they want.įormat node storage as XFS with the ftype=1 option. There is no longer a need to specify or configure the overlay driver. OverlayFS is now the default in Docker CE. It should be absent or set to false in a Docker configuration file.īefore installing Docker on CentOS/RHEL, review the general requirements and recommendations for running Docker on DC/OS and the following CentOS/RHEL-specific recommendations: Requirements and Recommendationsīe sure that Docker’s live-restore setting is disabled. NOTE: More specific details on the Docker bug and mitigation instructions are located here and here. Mesosphere DC/OS customers and community members who utilize RedHat or CentOS as their base operating systems are strongly advised to avoid this version. Mesosphere DC/OS customers and community members who utilize RedHat or CentOS as their base operating systems are strongly advised to either use RedHat’s fork of Docker 1.13 or Docker CE/EE 18.09.1 or later, neither of which are affected by the bug.Īnother kmem bug was introduced into version 1.2.10-3.2 of the package containerd.io which can affect any version of Docker. Customers may notice tasks or commands getting stuck indefinitely and kernel-related error messages in the system logs. A bug in Docker 17.x’s handling of cgroups kernel memory controller (kmem) causes instability for the entire system when the kmem accounting feature is activated.
0 Comments
Leave a Reply. |