vagrant - 输出 : mount. nfs:不支持请求的 NFS 版本或传输协议(protocol)

Question

我正在复制 Controller 示例 [1] 中尝试 Kubernetes NFS 卷声明。

我已经设置了 NFS 服务器、PV 和 PVC。我的复制 Controller 看起来像这样

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

当我尝试部署 Replication Controller 时，容器处于 ContainerCreating 状态，我可以在 minion 的日志中看到以下错误

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] - https://github.com/kubernetes/kubernetes/tree/master/examples/nfs

[2] - https://github.com/pires/kubernetes-vagrant-coreos-cluster

Answer 1

我遇到了同样的问题，然后意识到 nfs-server.service 状态已禁用。激活后，问题已解决。