Closed Manouchehri closed 6 years ago
@Manouchehri is the /dev dir in the VIC bound to the photon container, that would be needed if the photon-DCH can see the /dev/disk.... files to be able to mount the attached volume inside the container. The vDVS plugin does have /dev bound to it but in this case thats just the /dev inside the photon-DCH which can't see the devices attached to the VIC-container.
You would need to run the photon-DCH with the /dev of VIC bound to it and the vDVS plugin will need an enhancement to use an env var. to select the location at which to find the volume devices.
What's the use case that requires using VIC to run docker hosts? Is it to by-pass say a vSphere client to provision VMs on ESX hosts?
Closing as we don't have a use case that needs this support.
While obviously vDVS won't work on VIC (no plugin support), it'd be nice if there was support for Docker Container Host (DCH) deployments (DinV).
Steps to reproduce:
10.0.10.2
is the DCH.Related to #56.