This repository was archived by the owner on Dec 7, 2023. It is now read-only.
This repository was archived by the owner on Dec 7, 2023. It is now read-only.
Mounting volume device using the --volumes flag not working #646
Description
Hello Weaveworks team,
I am trying to start a VM that uses the --volume flag to mount a disk device inside a VM, but all attempts to make this work are futile. Here is what I do:
# Create loop device
dd if=/dev/zero of=/test_vol/diskimage bs=1M count=1024
# Make it a ext4 FS
mkfs.ext4 /test_vol/diskimage
# Set up the loop device
sudo losetup /dev/loop17 /test_vol/diskimage
# Start Ignite with the --volume flag (the loop device is not mounted locally, my understanding is that Ignite / Firecracker will mount it inside the VM)
sudo ignite \
run weaveworks/ignite-kubeadm:latest \
--network-plugin cni \
--cpus 2 \
--memory 2GB \
--ssh \
--volumes /dev/loop17:/dev/loop1 \
--name master-1
Here is the output of the command:
INFO[0000] Created VM with ID "e2c782438e20f3f3" and name "master-1"
INFO[0001] Networking is handled by "cni"
INFO[0001] Started Firecracker VM "e2c782438e20f3f3" in a container with ID "ignite-e2c782438e20f3f3"
INFO[0002] Waiting for the ssh daemon within the VM to start...
INFO[0013] Waiting for the ssh daemon within the VM to start...
INFO[0023] Waiting for the ssh daemon within the VM to start...
FATA[0033] dial tcp 10.50.59.6:22: connect: connection refused
There is no documentation on how to use the --volumes flag, I did try all sorts of variations to make this work, but nothing helps. Can someone help me out on this please?
BR