The configuration of "Docker Host" VMs is stored on your pool in a hidden directory at
/mnt/<pool name>/.bhyve_containers
Recovering a "Docker Host" VM may be possible by copying an existing config to a newly created "Docker Host". It's the
device.map and
grub.cfg that need to be copied.
You cannot do the recovery via the webUI alone, old or new. You cannot pick a pre-exiting RAW file when creating a "Docker Host" VM, or simply edit the RAW device after using the wizard. The "Docker Host" VM configuration and RAW file are not created on the pool until the VM is started for the first time.
So in order to copy the underlying config of your inaccessible docker VM you have to go through all steps of creating and starting once a new "Docker Host".
First check your RancherVM config is still on you pool. e.g. with:
ll -R /mnt/<pool name>/.bhyve_containers
Here's an exmaple:
Code:
root@freenas:/ # ll -R /mnt/NasPool/.bhyve_containers
total 1
drwxr-xr-x 3 root wheel 3 Sep 15 09:35 configs/
drwxr-xr-x 2 root wheel 4 Sep 12 12:20 iso_files/
/mnt/NasPool/.bhyve_containers/configs:
total 1
drwxr-xr-x 3 root wheel 4 Sep 15 09:35 27_dockerA/
/mnt/NasPool/.bhyve_containers/configs/27_dockerA:
total 1
-rw-r--r-- 1 root wheel 38 Sep 15 09:35 device.map
drwxr-xr-x 2 root wheel 3 Sep 15 09:35 grub/
/mnt/NasPool/.bhyve_containers/configs/27_dockerA/grub:
total 5
-rw-r--r-- 1 root wheel 294 Sep 15 09:35 grub.cfg
/mnt/NasPool/.bhyve_containers/iso_files:
total 117713
-rw-r--r-- 1 root wheel 47958299 Jul 28 15:47 rancheros-bhyve-v1.1.3.img.gz
-rw-r--r-- 1 root wheel 73924582 Sep 12 12:20 rancheros-bhyve-v1.4.0.img.gz
If it exists, then check the contents of
device.map and that it references a RAW file that is still on your pool. In my example it is:
Code:
root@freenas:/mnt/NasPool/.bhyve_containers/configs/27_dockerA # cat device.map
(hd0) mnt/NasPool2/VM/dockerA_dockerA
IIRC, BETA2 was still using the rancheros-bhyve-v1.1.3.img.gz. Is that still on your pool?