Provision Docker Storage on a Dedicated Block Device: Difference between revisions
| Line 15: | Line 15: | ||
[[Wipefs#Erase_all_Signatures|Erase all signatures]] from the partition. | [[Wipefs#Erase_all_Signatures|Erase all signatures]] from the partition. | ||
Initialize the partition for use by LVM. | [[pvcreate#Initialize_Partition_for_use_by_LVM|Initialize the partition for use by LVM]]. | ||
Revision as of 03:03, 23 May 2017
Internal
Overview
Procedure
Provision an unformatted block device. For this example, it will be referred to as /dev/sdb.
Create one partition that spans the entire device. Either fdisk or sfdisk can be used. This is how the partition is created with fdisk.
The procedure will create a /dev/sdb1 partition.
Erase all signatures from the partition.
Initialize the partition for use by LVM.
pvcreate /dev/sdb1
Verify your configuration. You should have a dm.thinpooldev value in the /etc/sysconfig/docker-storage file and a docker-pool logical volume:
# cat /etc/sysconfig/docker-storage DOCKER_STORAGE_OPTIONS=--storage-opt dm.fs=xfs --storage-opt dm.thinpooldev=/dev/mapper/docker--vg-docker--pool # lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert docker-pool rhel twi-a-t--- 9.29g 0.00 0.12
Before using Docker or OpenShift Container Platform, verify that the docker-pool logical volume is large enough to meet your needs. The docker-pool volume should be 60% of the available volume group and will grow to fill the volume group via LVM monitoring.