Page History

• Recommended size for KOP persistent volume is 50 Gb
• Try to specify an independent disk/partition, so you can easily increase it later if needed

Special requirements for RedHat, CentOS and Fedora

If your docker server is running on RedHat, CentOS or Fedora, be sure your the filesystem where docker is installed supports d_type.

Some installation of above operating systems aren't configured with d_type support (see http://www.pimwiddershoven.nl/entry/docker-on-centos-7-machine-with-xfs-filesystem-can-cause-trouble-when-d-type-is-not-supported) 

Running on XFS without d_type support causes Docker to skip the attempt to use the overlay or overlay2 driver.

Existing installs will continue to run, but produce an error. 

Some installation of above operating systems aren't configured with d_type support (see http://www.pimwiddershoven.nl/entry/docker-on-centos-7-machine-with-xfs-filesystem-can-cause-trouble-when-d-type-is-not-supported) 

Running on XFS without d_type support causes Docker to skip the attempt to use the overlay or overlay2 driver.

Existing installs will continue to run, but produce an error. See https://docs.docker.com/storage/storagedriver/overlayfs-driver/#prerequisites 

You can check if your existing XFS filesystem has d_type enabled by running these commands

$ docker info | grep "Supports d_type:"
Supports d_type: true

$ xfs_info /docker-mount-point | grep ftype 
naming =version 2         bsize=4096      ascii-ci=0     ftype=1

In case you get d_type: false or  ftype=0 , you have to create a new XFS filesystem with d_type support enabled.

Unfortunately, it isn't possible to enable d_type support on an existing filesystem.

You have two options:

1. either you add a new disk and you create a new XFS partition on it, or
2. you've to backup your existing data and recreate the XFS filesystem with d_type support enabled. 
   

Creating a new XFS filesystem with d_type enabled is as easy at the following command:

$ mkfs.xfs -n ftype=1 /mount-point