This repository has been archived by the owner on Nov 9, 2020. It is now read-only.
Incorrect dockvols location for VMs in nested folders in datastore #449
Labels
Milestone
Comments
msterin
pushed a commit
that referenced
this issue
Jun 9, 2016
msterin
pushed a commit
that referenced
this issue
Jun 10, 2016
…by Name Place dockvols to datastore root - Fixe #449. Also , if VM as renamed, the whole "find VM" mechanism was confused - so I fixed by by using search by UUID rather than scan for name. It has a side effect of being faster (on 10 VMs query time dropped from 0.25 sec to 0.05 sec)
msterin
pushed a commit
that referenced
this issue
Jun 10, 2016
…by Name Place dockvols to datastore root - Fixe #449. Also , if VM as renamed, the whole "find VM" mechanism was confused - so I fixed by by using search by UUID rather than scan for name. It has a side effect of being faster (on 10 VMs query time dropped from 0.25 sec to 0.05 sec)
msterin
pushed a commit
that referenced
this issue
Jun 11, 2016
…by Name Place dockvols to datastore root - Fixe #449. Also , if VM as renamed, the whole "find VM" mechanism was confused - so I fixed by by using search by UUID rather than scan for name. It has a side effect of being faster (on 10 VMs query time dropped from 0.25 sec to 0.05 sec)
msterin
pushed a commit
that referenced
this issue
Jun 11, 2016
…by Name Place dockvols to datastore root - Fixe #449. Also , if VM as renamed, the whole "find VM" mechanism was confused - so I fixed by by using search by UUID rather than scan for name. It has a side effect of being faster (on 10 VMs query time dropped from 0.25 sec to 0.05 sec)
msterin
pushed a commit
that referenced
this issue
Jun 11, 2016
…by Name Place dockvols to datastore root - Fixe #449. Also , if VM as renamed, the whole "find VM" mechanism was confused - so I fixed by by using search by UUID rather than scan for name. It has a side effect of being faster (on 10 VMs query time dropped from 0.25 sec to 0.05 sec)
msterin
pushed a commit
that referenced
this issue
Jun 11, 2016
…by Name Place dockvols to datastore root - Fixe #449. Also , if VM as renamed, the whole "find VM" mechanism was confused - so I fixed by by using search by UUID rather than scan for name. It has a side effect of being faster (on 10 VMs query time dropped from 0.25 sec to 0.05 sec)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
VM1: /vmfs/volumes/Storage1/Photon1.vmx
VM2: /vmfs/volumes/Storage1/test/abc/Photon2.vmx
Docker volumes created by VM1 are stored in;
Docker volumes created by VM2 are stored in;
docker volume ls
from VM1 reports volumes in/vmfs/volumes/Storage1/dockvols
docker volume ls
from VM2 reports volumes in/vmfs/volumes/Storage1/test/abc/dockvols
We should always be creating dockvols in
datastore\dockvols
rather than in parent directory.We can get VM datastore info from VirtualMachineConfigSummary.summary.config.vmPathName and use it to create "dockvols" directory.
This issue also has other side effects for e.g. volume creation and mounting works fine for Photon2.vmx but unmount/detach fails. with following error;
The text was updated successfully, but these errors were encountered: