kubernetes 1.2.0版本之kubelet啓動報錯:linux
I0316 21:39:13.701857 60146 kubelet.go:2381] skipping pod synchronization - [container runtime is down]docker E0316 21:39:14.216490 60146 kubelet.go:2726] Container runtime sanity check failed: container runtime version is older than 1.18centos |
看了下docker的版本,以前kubernetes 1.1.0是沒有問題的api
[root@localhost ~]# docker version測試 Client version: 1.5.0ui Client API version: 1.17spa Go version (client): go1.3.3.net Git commit (client): a8a31ef/1.5.0server OS/Arch (client): linux/amd64ip Server version: 1.5.0 Server API version: 1.17 Go version (server): go1.3.3 Git commit (server): a8a31ef/1.5.0 |
感受是說Client API version,比較低,kube 1.2.0不支持???
確認是kube 1.2版本的須要docker的api版本是大於1.18,如今docker版本爲:
[root@localhost ~]# docker version Client: Version: 1.8.2-el7.centos API version: 1.20 Package Version: docker-1.8.2-10.el7.centos.x86_64 Go version: go1.4.2 Git commit: a01dc02/1.8.2 Built: OS/Arch: linux/amd64
Server: Version: 1.8.2-el7.centos API version: 1.20 Package Version: Go version: go1.4.2 Git commit: a01dc02/1.8.2 Built: OS/Arch: linux/amd64 |
總結:
一、kubernetes 1.2版本,變更幅度較於kubernetes 1.1的大,能夠做爲嚐鮮測試
二、kubernetes 1.2版本的須要docker的api版本是大於1.18的,可根據狀況升級對應的docker版本