首页 > 解决方案 > VPN 上的 minikube 挂载中断

问题描述

所以我在使用 Big-IP VPN 时遇到了 minikube mount 命令的问题。基本上,该命令看起来像是能够通过 ssh 进入 minikube 虚拟机,但无论出于何种原因,minikube 都无法挂载主机文件夹。

$ minikube mount --v=10 app_shared_sec:/app/shared/sec
Mounting app_shared_sec into /app/shared/sec on the minikube VM
This daemon process needs to stay alive for the mount to still be accessible...
ufs starting
Using SSH client type: native
&{{{<nil> 0 [] [] []} docker [0x140f940] 0x140f910  [] 0s} 127.0.0.1 57930 <nil> <nil>}
About to run SSH command:
sudo umount /app/shared/sec;
SSH cmd err, output: Process exited with status 32: umount: /app/shared/sec: not mounted.

Using SSH client type: native
&{{{<nil> 0 [] [] []} docker [0x140f940] 0x140f910  [] 0s} 127.0.0.1 57930 <nil> <nil>}
About to run SSH command:

sudo mkdir -p /app/shared/sec || true;
sudo mount -t 9p -o trans=tcp,port=51501,dfltuid=1001,dfltgid=1001,version=9p2000.u,msize=262144 192.168.99.1 /app/shared/sec;
sudo chmod 775 /app/shared/sec || true;
SSH cmd err, output: <nil>: mount: /app/shared/sec: mount(2) system call failed: Connection timed out.

在 minikube VM 中运行netstat似乎表明它能够读取主机。

$ netstat -nr
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         10.0.2.2        0.0.0.0         UG        0 0          0 eth0
10.0.2.0        0.0.0.0         255.255.255.0   U         0 0          0 eth0
10.0.2.2        0.0.0.0         255.255.255.255 UH        0 0          0 eth0
172.17.0.0      0.0.0.0         255.255.0.0     U         0 0          0 docker0
192.168.99.0    0.0.0.0         255.255.255.0   U         0 0          0 eth1

问题似乎是因为 VPN 炸毁了主机上的 vboxnet 接口,minikube VM 无法与之通信,导致挂载失败。当尝试重新创建路由时,Big-IP 似乎会注意更改并将其删除。不知道此时还能做什么。

标签: kubernetesvpnminikube

解决方案


推荐阅读