IsVDVSRunningAfterVMRestart() is added to utils/esx via #1563, but the managed plugin should be moved to utils/docker as its a docker managed plugin and it also needs to check that docker itself is up after a VM is powered on besides checking for just the plugin.
The check itself is weak, it checks if a process exists for the plugin, while it takes a good 20 seconds after the plugin starts for it to be ready to handle mounts/unmounts reliably. There has to be a way to (via the docker volume commands) to be able to figure if the plugin is really ready.
IsVDVSRunningAfterVMRestart() is added to utils/esx via #1563, but the managed plugin should be moved to utils/docker as its a docker managed plugin and it also needs to check that docker itself is up after a VM is powered on besides checking for just the plugin.
The check itself is weak, it checks if a process exists for the plugin, while it takes a good 20 seconds after the plugin starts for it to be ready to handle mounts/unmounts reliably. There has to be a way to (via the docker volume commands) to be able to figure if the plugin is really ready.