<![CDATA[linuxの飘扬]]>

<![CDATA[linuxの飘扬]]> https://www.linuxfly.org/index.php zh-cn https://www.linuxfly.org/kubernetes-19-conflict-with-centos7/ <![CDATA[【原】kubernetes 1.9 与 CentOS 7.3 内核兼容问题]]> linuxing <emos#linuxfly.org> Fri, 30 Mar 2018 12:39:02 +0000 https://www.linuxfly.org/kubernetes-19-conflict-with-centos7/ 典型报错：

引用

kubelet.ns-k8s-node001.root.log.ERROR.20180214-113740.15702:1593018:E0320 04:59:09.572336 15702 remote_runtime.go:92] RunPodSandbox from runtime service failed: rpc error: code = Unknown desc = failed to start sa
ndbox container for pod "osp-xxx-com-ljqm19-54bf7678b8-bvz9s": Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "process_linux.go:258: applying cgroup configuration
for process caused \"mkdir /sys/fs/cgroup/memory/kubepods/burstable/podf1bd9e87-1ef2-11e8-afd3-fa163ecf2dce/8710c146b3c8b52f5da62e222273703b1e3d54a6a6270a0ea7ce1b194f1b5053: no space left on device\""

或者

引用

Mar 26 18:36:59 ns-k8s-node-s0054 kernel: SLUB: Unable to allocate memory on node -1 (gfp=0x8020)
Mar 26 18:36:59 ns-k8s-noah-node001 kernel: cache: ip6_dst_cache(1995:6b6bc0c9f30123084a409d89a300b017d26ee5e2c3ac8a02c295c378f3dbfa5f), object size: 448, buffer size: 448, default order: 2, min order: 0

该问题发生前后，进行过 kubernetes 1.6 到 1.9 的升级工作。怀疑问题与 kubernetes 、内核有关。
............

Tags - kubernetes , docker ]]> https://www.linuxfly.org/kubernetes-19-conflict-with-centos7/#blogcomment6498 <![CDATA[[评论] 【原】kubernetes 1.9 与 CentOS 7.3 内核兼容问题]]> bai <user@domain.com> Sun, 01 Jul 2018 16:30:29 +0000 https://www.linuxfly.org/kubernetes-19-conflict-with-centos7/#blogcomment6498 https://www.linuxfly.org/kubernetes-19-conflict-with-centos7/#blogcomment6548 <![CDATA[[评论] 【原】kubernetes 1.9 与 CentOS 7.3 内核兼容问题]]> dotDuck <user@domain.com> Mon, 25 Mar 2019 07:31:18 +0000 https://www.linuxfly.org/kubernetes-19-conflict-with-centos7/#blogcomment6548