minikube: mount: unknown filesystem type '9p'
mount problems after update of docker desktop to 2.3.0.2 and minikube update. Before it was also not stable as it timed out randomly
minikube start
- minikube v1.10.1 on Microsoft Windows 10 Enterprise 10.0.18363 Build 18363
- Using the docker driver based on existing profile
- Kubernetes 1.18.2 is now available. If you would like to upgrade, specify: --kubernetes-version=1.18.2
- Kubernetes 1.18.2 is now available. If you would like to upgrade, specify: --kubernetes-version=1.18.2
- Starting control plane node minikube in cluster minikube
- Restarting existing docker container for “minikube” …
- Preparing Kubernetes v1.18.0 on Docker 19.03.2 …
- kubeadm.pod-network-cidr=10.244.0.0/16
- Enabled addons: dashboard, default-storageclass, storage-provisioner
- Done! kubectl is now configured to use “minikube” Steps to reproduce the issue:
- minikube start
- minikube mount -> error
Full output of failed command: minikube mount “C:\tmp\mqdocker:/mqdocker”
- Mounting host path C:\tmp\mqdocker into VM as /mqdocker …
- 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:50922
- 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=50922,trans=tcp,version=9p2000.L 192.168.65.2 /mqdocker” : /bin/bash -c “sudo mount -t 9p -o dfltgid=$(grep ^docker: /etc/group | cut -d: -f3),dfltuid=$(id -u docker),msize=262144,port=50922,trans=tcp,version=9p2000.L 192.168.65.2 /mqdocker”: Process exited with status 32 stdout:
stderr: mount: /mqdocker: unknown filesystem type ‘9p’.
Full output of minikube start command used, if not already included:
Optional: Full output of minikube logs command:
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 7
- Comments: 16 (1 by maintainers)
/remove-lifecycle stale
Also experiencing with Minikube running on CentOS 7.