4/30/2023 0 Comments Docker convoy plugin![]() ![]() You can take a look here if you want to know how much storage should be allocated for the metadata device.įirst, mount the NFS share to the root directory used to store volumes.You can override it with the -driver-opts dm.defaultvolumesize option. The default Device Mapper volume size is 100G. ![]() Assuming you have two devices created one data device called /dev/convoy-vg/data and the other metadata device called /dev/convoy-vg/metadata, then run the following command to start the Convoy daemon: sudo convoy daemon -drivers devicemapper -driver-opts dm.datadev=/dev/convoy-vg/data -driver-opts dm.metadatadev=/dev/convoy-vg/metadata See Device Mapper Partition Helper for more details.ĭevice Mapper requires two block devices to create storage pool for all volumes and snapshots. Then you can make two partitions on the device using dm_dev_partition.sh to get two block devices ready for the Device Mapper driver. If you're running in a production environment with the Device Mapper driver, it's recommended to attach a new, empty block device to the host Convoy is running on. You need to pass different arguments to the Convoy daemon depending on your choice of back-end implementation. Run the following commands to set up the Convoy volume plugin for Docker: sudo mkdir -p /etc/docker/plugins/ Put the binaries in a directory in the execution $PATH of sudo and root users (e.g. InstallationĮnsure you have Docker 1.8 or above installed.ĭownload the latest version of Convoy and unzip it. You should see the recovered file in /res1/foo. ![]() The following command creates a new container and mounts the recovered Convoy volume into that container: sudo docker run -v res1:/res1 -volume-driver=convoy ubuntu ls /res1/foo You can use this URL to recover the volume on another host: sudo convoy create res1 -backup The convoy backup command returns a URL string representing the backup dataset. Sudo convoy backup create snap1vol1 -dest vfs:///opt/convoy/ Next, take a snapshot of the convoy volume and backup the snapshot to a local directory: (You can also make backups to an NFS share or S3 object store.) sudo convoy snapshot create vol1 -name snap1vol1 As a test, create a file called /vol1/foo in the Convoy volume: sudo docker run -v vol1:/vol1 -volume-driver=convoy ubuntu touch /vol1/foo You can create a Docker container with a convoy volume. Once the data and metadata devices are set up, you can start the Convoy plugin daemon as follows: sudo convoy daemon -drivers devicemapper -driver-opts dm.datadev=/dev/loop5 -driver-opts dm.metadatadev=/dev/loop6 A loopback device, however, is known to be unstable and should not be used in production. You can use a file-backed loopback device to test and demo Convoy Device Mapper driver. Sudo bash -c 'echo "unix:///var/run/convoy/convoy.sock" > /etc/docker/plugins/convoy.spec' Sudo cp convoy/convoy convoy/convoy-pdata_tools /usr/local/bin/ Once the right Docker daemon version is running, install and configure the Convoy volume plugin as follows: wget If not, install the latest Docker daemon as follows: curl -sSL | sh
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |