k8s 常见问题大收集

[root@docker docker]# docker push 10.0.0.10:5000/test/nginx:v1

The push refers to repository [10.0.0.10:5000/test/nginx]

Get https://10.0.0.10:5000/v2/: http: server gave HTTP response to HTTPS client

2.1.1、解决方法 1：（docker 1.2 以上版本解决方法）

在/etc/docker/daemon.json 添加以下信息

{ "insecure-registries":["10.0.0.10:5000"] 必须要加在第一行

重启 docker，重启 registry

systemctl restart docker.service

2.1.2、解决方法 2：（docker1.2 以下版本解决方法）

报错信息 2：

[root@lnmp ~]# docker pull 10.0.0.10:5000/test/nginx:v1

Error response from daemon: invalid registry endpoint https://10.0.0.10:5000/v0/: unable to ping registry endpoint https://10.0.0.10:5000/v0/

v2 ping attempt failed with error: Get https://10.0.0.10:5000/v2/: tls: oversized record received with length 20527

v1 ping attempt failed with error: Get https://10.0.0.10:5000/v1/_ping: tls: oversized record received with length 20527. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add --insecure-registry 10.0.0.10:5000 to the daemon's arguments. In the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag; simply place the CA certificate at /etc/docker/certs.d/10.0.0.10:5000/ca.crt

2.2、解决办法：

在/etc/sysconfig/docker 中添加如下信息即可

other_args="--insecure-registry 10.0.0.10:5000" 私有仓库地址

other_args="--insecure-registry registry:5000" 公有仓库地址

重启 docker，重启 registry

/etc/init.d/docker restart

第 3 章 下载镜像出现问题

3.1、问题 1：提示/etc/rhsm/ca/redhat-uep.pem no file or dirctory

3.1.1、解决方法：

3.1.1.1、yum 安装需要的依赖包

yum -y install rhsm

3.1.1.2、下载 python-rhsm-certificates 软件并生成密钥文件

wget http://mirror.centos.org/centos/7/os/x86_64/Packages/python-rhsm-certificates-1.19.10-1.el7_4.x86_64.rpm

生成密钥

rpm2cpio python-rhsm-certificates-1.19.10-1.el7_4.x86_64.rpm | cpio -iv --to-stdout ./etc/rhsm/ca/redhat-uep.pem | tee /etc/rhsm/ca/redhat-uep.pem

3.1.1.3、重新 pull 镜像

docker pull registry.access.redhat.com/rhel7/pod-infrastructure:latest

第 4 章 不能删除容器

4.1、docker 报错 rpc error: code = 14 desc = grpc: the connection is unavailable

4.1.1、尝试关闭容器，进入容器操作界面也报相同错误：

[root@k8s-node-1 ~]# docker exec -it 7119f8f5feef /bin/bash

rpc error: code = 14 desc = grpc: the connection is unavailable

4.1.1.2、停止容器依旧提示错误

[root@k8s-node-1 ~]# docker stop 7119f8f5feef

Error response from daemon: Cannot stop container 7119f8f5feef: Cannot kill container 7119f8f5feef4c649d9ec04734e6224e2d837fa030de271f269f0b71eea29327: rpc error: code = 14 desc = grpc: the connection is unavailable

4.1.1.3、删除容器依旧提示错误（-f 强制删除）

[root@k8s-node-1 ~]# docker rm -f 7119f8f5feef

Error response from daemon: Could not kill running container 7119f8f5feef4c649d9ec04734e6224e2d837fa030de271f269f0b71eea29327, cannot remove - Cannot kill container 7119f8f5feef4c649d9ec04734e6224e2d837fa030de271f269f0b71eea29327: rpc error: code = 14 desc = grpc: the connection is unavailable

4.2、解决办法：

4.2.1、使用 docker-containerd 命令以 debug 模式调试容器

注意：那个 node 上的容器不能删除就在那台 node 上面执行以下命令

[root@k8s-node-1 ~]# docker-containerd -l unix:///var/run/docker/libcontainerd/docker-containerd.sock --metrics-interval=0 --start-timeout 2m --state-dir /var/run/docker/libcontainerd/containerd --shim docker-containerd-shim --runtime docker-runc --debug

WARN[0000] containerd: low RLIMIT_NOFILE changing to max current=1024 max=4096

DEBU[0000] containerd: read past events count=1

low RLIMIT_NOFILE changing to max current=1024 max=4096DEBU[0000] containerd: grpc api on /var/run/docker/libcontainerd/docker-containerd.sock

DEBU[0000] containerd: container restored id=354af53914e3f76e653a26d9e9da8d4fbef4ef18cc2176371b89871a9126a646

DEBU[0000] containerd: container restored id=3f0bf43f7ca97c439b64370cee09205b35e58ed35e49f957412f58affbe4ed4b

DEBU[0000] containerd: container restored id=4b848d33a32a332635929b95eb7291abeb32f177a3c65248568b959dbfbc2712

DEBU[0000] containerd: container restored id=4ed8d1f971a0ea5035b507511d802a1445af9e771cde670814104102a7cc2d6f

ERRO[0000] containerd: notify OOM events error=open /proc/13541/cgroup: no such file or directory

DEBU[0000] containerd: container restored id=7119f8f5feef4c649d9ec04734e6224e2d837fa030de271f269f0b71eea29327

ERRO[0000] containerd: notify OOM events error=open /proc/12860/cgroup: no such file or directory

DEBU[0000] containerd: container restored id=7bdba0a1ee81997bdbb5958e31123538ac8a6730c6cc7120fe7359439b52b410

DEBU[0000] containerd: container restored id=8ba79a79836b4350335375f89fc1473a6a86593375fbac6344fb17e4dddff43f

DEBU[0000] containerd: container restored id=9692f3570460186de681476bd068d008891b24b3906f190443f24e97343c3e57

DEBU[0000] containerd: supervisor running cpus=1 memory=977 runtime=docker-runc runtimeArgs=[] stateDir=/var/run/docker/libcontainerd/containerd

DEBU[0000] containerd: process exited id=7119f8f5feef4c649d9ec04734e6224e2d837fa030de271f269f0b71eea29327 pid=init status=143 systemPid=13541

ERRO[0000] containerd: deleting container error=exit status 1: "container 7119f8f5feef4c649d9ec04734e6224e2d837fa030de271f269f0b71eea29327 does not exist\none or more of the container deletions failed\n"

DEBU[0000] containerd: process exited id=7bdba0a1ee81997bdbb5958e31123538ac8a6730c6cc7120fe7359439b52b410 pid=init status=137 systemPid=12860

ERRO[0000] containerd: deleting container error=exit status 1: "container 7bdba0a1ee81997bdbb5958e31123538ac8a6730c6cc7120fe7359439b52b410 does not exist\none or more of the container deletions failed\n"

^CINFO[0056] stopping containerd after receiving interrupt

4.2.2、调试后发现容器状态变为了未开启，尝试删除容器，成功

docker exec -it 3e22bd0b6a40 /bin/bash

Error response from daemon: Container 3e22bd0b6a40c85d2af45b5d65fb3648acab7e0ad05fa909201051a8f00a3d15 is not running

docker rm -f zen_mclean

zen_mclean

第 5 章 k8s 下 DNS 问题

5.1、kubelet 提示 DNS 错误信息

kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. Fail

5.2、解决办法：

在 cat /etc/kubernetes/kubelet 配置文件中添加如下内容即可

KUBE_ARGS="--cluster-dns=10.0.0.110 --cluster-domain=cluster.local"

重启 systemctl daemon-reload; systemctl restart kubelet 即可

第 6 章 docker run （镜像）报错，文件系统

【一线大厂Java面试题解析+后端开发学习笔记+最新架构讲解视频+实战项目源码讲义】
浏览器打开：qq.cn.hn/FTf 免费领取

不支持

1、报错信息如下：

/usr/bin/docker-current: Error response from daemon: error creating overlay mount to /var/lib/docker/overlay2/7b4a1ef8a539785fde3fa4cabc4bb9d90967a30calid argument.

See '/usr/bin/docker-current run --help'.

2、报错原因

这个是因为用的 overlay2 文件系统，而系统默认只能识别 overlay 文件系统

所以我们就要更新文件系统了

3、解决方法：

systemctl stop docker //停掉 docker 服务