vmware-vdiskmanager not installed

[kjpruden]

Host: MacBook Pro (intel i5) on MacOS 12.6.1

Version: Professional Version e.x.p (20486664)

I recently installed the tech preview of VMWare fusion intending to use it with minikube to manage a k8s cluster. This isn't working, and I've traced the problem down to the vmware-vdiskmanager binary being missing:

$ ls "/Applications/VMware Fusion Tech Preview.app/Contents/Public"
containerd docker-machine-driver-vmware libvixAllProducts.dylib swagger.zip vmrest
containerd-shim-crx-v2 include open_source_licenses.txt vctl vmrun

According to all of the documentation I can find, this utility should be included. Has anyone else encountered this issue, and is there a solution?

Thanks!

Kris

[palter]

vmware-vdiskmanager is in /Applications/VMware Fusion Tech Preview.app/Contents/Library/

[kjpruden]

Oh, thanks!

Do you know what the difference is between ".../Content/Library" and ".../Content/Public"?

It looks like the latter contains mostly symlinks to binaries in the former:

$ ls -l "/Applications/VMware Fusion Tech Preview.app/Contents/Public"
total 3536
lrw-r--r--@ 1 root wheel 29 Sep 19 07:30 containerd -> ../Library/vkd/bin/containerd
lrw-r--r--@ 1 root wheel 41 Sep 19 07:30 containerd-shim-crx-v2 -> ../Library/vkd/bin/containerd-shim-crx-v2
lrw-r--r--@ 1 root wheel 47 Sep 19 07:30 docker-machine-driver-vmware -> ../Library/vkd/bin/docker-machine-driver-vmware
drwxr-xr-x 5 root wheel 160 Sep 19 07:20 include
-rw-r--r-- 1 root wheel 1657792 Sep 19 07:23 libvixAllProducts.dylib
-rw-r--r-- 1 root wheel 149333 Sep 19 07:20 open_source_licenses.txt
lrw-r--r--@ 1 root wheel 22 Sep 19 07:30 swagger.zip -> ../Library/swagger.zip
lrw-r--r--@ 1 root wheel 23 Sep 19 07:30 vctl -> ../Library/vkd/bin/vctl
lrw-r--r--@ 1 root wheel 17 Sep 19 07:30 vmrest -> ../Library/vmrest
lrw-r--r--@ 1 root wheel 16 Sep 19 07:30 vmrun -> ../Library/vmrun

The installer puts the "Public" directly in the PATH, so I assume that's where I should expect to find things. I can add "Library" to my PATH easily enough, but this seems like a bug in the installer..

[AlessandroDN]

Do you know what the difference is between ".../Content/Library" and ".../Content/Public"?

The content of `Public` is available in the shell without the need to remember the whole path (e.g. you can type `vmrun` directly).

Actually, I always add commands that I often use in the `Public` folder: so, for example

cd "/Applications/VMware Fusion.app/Contents/Public/"
ln -s ../Library/vmware-vdiskmanager

And you can use `vmware-vdiskmanager` without remembering its path 😉