Kubernetes pod未将卷绑定到容器

Question

我已经定义了以下复制控制器JSON:

{
  "id": "PHPController",
  "kind": "ReplicationController",
  "apiVersion": "v1beta1",
  "desiredState": {
    "replicas": 2,
    "replicaSelector": {"name": "php"},
    "podTemplate": {
      "desiredState": {
         "manifest": {
           "version": "v1beta1",
           "id": "PHPController",
           "volumes": [{ "name": "wordpress", "path": "/mnt/nfs/wordpress_a", "hostDir": "/mnt/nfs/wordpress_a"}],
           "containers": [{
             "name": "php",
             "image": "internaluser/php53",
             "ports": [{"containerPort": 80, "hostPort": 9021}],
             "volumeMounts": [{"name": "wordpress", "mountPath": "/mnt/nfs/wordpress_a"}]
           }]
         }
       },
       "labels": {"name": "php"}
      }},
  "labels": {"name": "php"} 

}

使用“docker run-t-I-p 0 . 0 . 0 . 0:9021:80-v/mnt/NFS/WordPress _ a:/mnt/NFS/WordPress _ a:rw internal user/PHP 53”运行时，容器正确启动。

/mnt/nfs/wordpress_a是一个nfs共享，安装在所有的minions上。每个minion都有完全的RW访问权限，并且我已经验证了共享是存在的。

使用复制控制器创建pod容器后，我可以看到该卷从未实际绑定，和/或安装错误：

    "Volumes": {
        "/mnt/nfs/wordpress_a": "/var/lib/docker/vfs/dir/8b5dc8477958f5c1b894e68ab9412b41e81a34ef16dac81f0f9d4884352a90b7"
    },
    "VolumesRW": {
        "/mnt/nfs/wordpress_a": true
    }

    "HostConfig": {
        "Binds": null,
        "ContainerIDFile": "",
        "LxcConf": null,
        "Privileged": false,
        "PortBindings": {
            "80/tcp": [
                {
                    "HostIp": "",
                    "HostPort": "9021"
                }
            ]
        },

我觉得奇怪的是，容器认为 /mnt/nfs/wordpress_a映射到"/var/lib/docker/vfs/dir/8b5dc8477958f5c1b894e68ab9412b41e81a34ef16dac81f0f9d4884352a90b7"。

根据kubelet日志：

所需的[10 . 101 . 4 . 15]:[{ Namespace:etcd Name:c 823 da9e-4437-11e 4-a3 B1-0050568421 EB清单:{ Version:v1beta 1 ID:c 823 da9e-4437-11e 4-a3 B1-0050568421 EB UUID:c 823 da9e-4437-11e 4-a3 B1-0050568421 EB卷

有没有人有过这种事情的经验？我一直在疯狂地解决这个问题。谢谢！

Answer 1

解决了。卷语法不正确。https://github . com/Google cloud platform/kubernetes/issues/1446