I believe this is same as the hyperv issue that we had closed without fixing.
PS C:\Users\jenkins\actions-runner\_work\minikube\minikube\minikube_binaries> .\minikube-windows-amd64.exe mount -p minikube C:\Users\jenkins\actions-runner\_work\minikube\minikube\minikube_binaries:/mount-9p
* Mounting host path C:\Users\jenkins\actions-runner\_work\minikube\minikube\minikube_binaries into VM as /mount-9p ...
- Mount type: <no value>
- User ID: docker
- Group ID: docker
- Version: 9p2000.L
- Message Size: 262144
- Permissions: 755 (-rwxr-xr-x)
- Options: map[]
- Bind Address: 127.0.0.1:50211
* Userspace file server: ufs starting
*
X mount failed: mount with cmd /bin/bash -c "sudo mount -t 9p -o dfltgid=$(grep ^docker: /etc/group | cut -d: -f3),dfltuid=$(id -u docker),msize=262144,port=50211,trans=tcp,version=9p2000.L 192.168.65.2 /mount-9p" : /bin/bash -c "sudo mount -t 9p -o dfltgid=$(grep ^docker: /etc/group | cut -d: -f3),dfltuid=$(id -u docker),msize=262144,port=50211,trans=tcp,version=9p2000.L 192.168.65.2 /mount-9p": Process exited with status 32
stdout:
stderr:
mount: /mount-9p: unknown filesystem type '9p'.
*
* minikube is exiting due to an error. If the above message is not useful, open an issue:
- https://github.com/kubernetes/minikube/issues/new/choose
the root cause is not clear yet. but It could we need to add a powershell-exec runner
I believe this is same as the hyperv issue that we had closed without fixing.
the root cause is not clear yet. but It could we need to add a powershell-exec runner