Vagrant 输出:mount.nfs:不支持请求的nfs版本或传输协议
我正在复制控制器示例中尝试Kubernetes NFS卷声明[1] 我已经安装了NFS服务器、PV和PVC。我的复制控制器是这样的Vagrant 输出:mount.nfs:不支持请求的nfs版本或传输协议,vagrant,kubernetes,nfs,vagrantfile,Vagrant,Kubernetes,Nfs,Vagrantfile,我正在复制控制器示例中尝试Kubernetes NFS卷声明[1] 我已经安装了NFS服务器、PV和PVC。我的复制控制器是这样的 apiVersion: v1 kind: ReplicationController metadata: name: node-manager labels: name: node-manager spec: replicas: 1 selector: name: node-manager template: metada
apiVersion: v1
kind: ReplicationController
metadata:
name: node-manager
labels:
name: node-manager
spec:
replicas: 1
selector:
name: node-manager
template:
metadata:
labels:
name: node-manager
spec:
containers:
-
name: node-manager
image: org/node-manager-1.0.0:1.0.0
ports:
-
containerPort: 9763
protocol: "TCP"
-
containerPort: 9443
protocol: "TCP"
volumeMounts:
- name: nfs
mountPath: "/mnt/data"
volumes:
- name: nfs
persistentVolumeClaim:
claimName: nfs
当我尝试部署复制控制器时,容器处于ContainerCreating状态,我可以在仆从的日志中看到以下错误
Feb 26 11:39:41 node-01 kubelet[1529]: Mounting arguments: 172.17.8.102:/ /var/lib/kubelet/pods/0e66affa-dc79-11e5-89b3-080027f84891/volumes/kubernetes.io~nfs/nfs nfs []
Feb 26 11:39:41 node-01 kubelet[1529]: Output: mount.nfs: requested NFS version or transport protocol is not supported
Feb 26 11:39:41 node-01 kubelet[1529]: E0226 11:39:41.908756 1529 kubelet.go:1383] Unable to mount volumes for pod "node-manager-eemi2_default": exit status 32; skipping pod
Feb 26 11:39:41 node-01 kubelet[1529]: E0226 11:39:41.923297 1529 pod_workers.go:112] Error syncing pod 0e66affa-dc79-11e5-89b3-080027f84891, skipping: exit status 32
Feb 26 11:39:51 node-01 kubelet[1529]: E0226 11:39:51.904931 1529 mount_linux.go:103] Mount failed: exit status 32
使用[2]Kubernetes cluster vagrant cluster设置我的Kubernetes群集
我的仆从详情:
core@node-01 ~ $ cat /etc/lsb-release
DISTRIB_ID=CoreOS
DISTRIB_RELEASE=969.0.0
DISTRIB_CODENAME="Coeur Rouge"
DISTRIB_DESCRIPTION="CoreOS 969.0.0 (Coeur Rouge)"
[1] -
[2] -因此,为了解决此nfs装载版本问题,请在nfs服务器中的/etc/nfsmount.conf中输入Defaultvers=4。将解决此问题 我遇到了同样的问题,然后意识到nfs-server.service状态已禁用。激活后,问题已解决