在使用容器优化VM时,我面临一个问题。我使用以下命令启动一个实例:
gcloud compute instances create "$instance_name" \
--tags "http-server" \
--image container-vm \
--scopes storage-rw,logging-write \
--metadata-from-file google-container-manifest="m2.yml" \
--zone "$my_zone" \
--machine-type "$my_machine_type"其中m2.yml是:
version: v1beta2
containers:
- name: nginx
image: nginx当我对实例进行ssh并查看/var/log/docker.log时,我看到:
time="2015-06-17T07:42:59Z" level=error msg="Handler for GET /containers/{name:.*}/json returned error: no such id: kubelet"
time="2015-06-17T07:42:59Z" level=error msg="HTTP Error: statusCode=404 no such id: kubelet"
time="2015-06-17T07:42:59Z" level=info msg="GET /version"
time="2015-06-17T07:42:59Z" level=info msg="+job version()"
time="2015-06-17T07:42:59Z" level=info msg="-job version() = OK (0)"
time="2015-06-17T07:42:59Z" level=info msg="GET /containers/docker-daemon/json"
time="2015-06-17T07:42:59Z" level=info msg="+job container_inspect(docker-daemon)"
no such id: docker-daemon
time="2015-06-17T07:42:59Z" level=info msg="-job container_inspect(docker-daemon) = ERR (1)"
time="2015-06-17T07:42:59Z" level=error msg="Handler for GET /containers/{name:.*}/json returned error: no such id: docker-daemon"
time="2015-06-17T07:42:59Z" level=error msg="HTTP Error: statusCode=404 no such id: docker-daemon" 实例上没有运行容器,docker images -a说:
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
gcr.io/google_containers/pause 0.8.0 2c40b0526b63 11 weeks ago 241.7 kB
<none> <none> 56ba5533a2db 11 weeks ago 241.7 kB
<none> <none> 511136ea3c5a 2.009460 years ago 0 B集装箱发动机是出了什么问题还是我做错了什么?
Update1
我给了一个例子一次尝试:
version: v1 kind: Pod spec: containers: - name: simple-echo image: gcr.io/google_containers/busybox command: ['nc', '-p', '8080', '-l', '-l', '-e', 'echo', 'hello world!'] imagePullPolicy: Always ports: - containerPort: 8080 hostPort: 8080 protocol: TCP restartPolicy: Always dnsPolicy: Default
它仍然是日志中的错误:
evgeny@instance:~$ cat /var/log/docker.log | grep error
time="2015-06-18T16:28:56Z" level=error msg="Handler for GET /containers/{name:.*}/json returned error: no such id: kubelet"
time="2015-06-18T16:28:56Z" level=error msg="HTTP Error: statusCode=404 no such id: kubelet"
time="2015-06-18T16:28:56Z" level=error msg="Handler for GET /containers/{name:.*}/json returned error: no such id: docker-daemon"
time="2015-06-18T16:28:56Z" level=error msg="HTTP Error: statusCode=404 no such id: docker-daemon"
time="2015-06-18T16:28:56Z" level=error msg="Handler for GET /images/{name:.*}/json returned error: No such image: gcr.io/google_containers/busybox"
time="2015-06-18T16:28:56Z" level=error msg="HTTP Error: statusCode=404 No such image: gcr.io/google_containers/busybox"
time="2015-06-18T16:28:56Z" level=error msg="Handler for GET /containers/{name:.*}/json returned error: no such id: docker"
time="2015-06-18T16:28:56Z" level=error msg="HTTP Error: statusCode=404 no such id: docker"
time="2015-06-18T16:28:56Z" level=error msg="Handler for GET /images/{name:.*}/json returned error: No such image: gcr.io/google_containers/busybox"
time="2015-06-18T16:28:56Z" level=error msg="HTTP Error: statusCode=404 No such image: gcr.io/google_containers/busybox" 我正准备通过反馈表格发送反馈,但提交失败与:
relay__en.js?authuser=1:182 Uncaught TypeError: Cannot set property 'vmFeedbackData' of undefined。这样的故事。
发布于 2015-06-17 15:49:38
最新的容器vm映像不支持v1beta2 kubernetes API。您需要更新清单以使用v1beta3或v1 (以及相应的yaml更改)。
容器vm文档的最新版本显示了一个使用v1 API的yaml示例。
发布于 2016-07-08 00:13:50
我遇到了一个类似的问题,结果是我试图使用的解决方案。
securityContext:
privileged: trueKubernetes在不使用GoogleContainer集群(即在compute.v1.instance或compute.v1.instanceTemplate上使用一个compute.v1.instance元数据项)的情况下将停靠器映像加载到GCE实例时不遵守该属性,因此它从未正确地将映像加载到实例中。
移除那笔财产解决了我的问题。
https://stackoverflow.com/questions/30885922
复制相似问题