MicroK8s容器无法启动。所有吊舱都卡在“上”;“集装箱制造”;国家。Ubuntu 20.10 RP4
我一直在谷歌上搜索和浏览日志,试图解决这个问题,但我似乎无法让microk8s在运行Ubuntu 20.10的Raspberry Pi上运行 我快速安装v1.15 sudo快速安装microk8s——经典型——通道=1.15/稳定 我可以确认microk8s.status返回它正在运行。 kubectl get节点--命名空间kube系统返回:MicroK8s容器无法启动。所有吊舱都卡在“上”;“集装箱制造”;国家。Ubuntu 20.10 RP4,ubuntu,kubernetes,raspberry-pi,microk8s,ubuntu-20.10,Ubuntu,Kubernetes,Raspberry Pi,Microk8s,Ubuntu 20.10,我一直在谷歌上搜索和浏览日志,试图解决这个问题,但我似乎无法让microk8s在运行Ubuntu 20.10的Raspberry Pi上运行 我快速安装v1.15 sudo快速安装microk8s——经典型——通道=1.15/稳定 我可以确认microk8s.status返回它正在运行。 kubectl get节点--命名空间kube系统返回: NAME STATUS ROLES AGE VERSION mydnsname Ready <none&g
NAME STATUS ROLES AGE VERSION
mydnsname Ready <none> 22h v1.15.11
我已经检查过了,我没有使用ZFS作为我的主分区的文件系统,我使用的是overlayfs
df-Th
因此,考虑到containerd与overlayfs没有任何问题,我不确定containerd为什么不能安装或出现问题
已经尝试过microk8s.reset、卸载和重新安装,并尝试过几个不同的版本,但仍然无效
非常感谢任何想法或帮助,因为我渴望为本地开发人员获得本地kubernetes设置
提前谢谢 发现问题出在microk8s上,特别是containerd没有使用带覆盖的squashFS文件系统 我使用SquashFS安装Ubuntu的原因是我使用Berryboot支持多个操作系统安装 我切换到Pinn,它支持ext4文件系统,与containerd一起工作,并重新安装了Ubuntu20.04
安装microk8s后,节点开始运行,容器现在都正常运行。尝试microk8s启用dns,然后重置群集Hi Furkan,我尝试启用dns microk8s启用dns,然后重新启动microk8s-这就是您所说的重置群集吗?microk8s停止和microk8s启动CoreDNS容器仍显示相同的错误和容器创建状态。“创建pod沙盒失败:rpc错误”谢谢我的意思是“microk8s重置”,它应该重新安装所有东西。microk8s启用dns正常。但你做的事情也很相似。也许我错了。谢谢你的澄清。我尝试了microk8s重置并再次启用dns,但仍然存在相同的错误。另外,我尝试过重置和卸载microk8s,但同样的问题总是发生。我认为这可能与containerd未能装载根文件系统有关
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system pod/heapster-v1.5.2-c4dcfd9f8-kl5g5 0/4 ContainerCreating 0 68s
kube-system pod/kubernetes-dashboard-c775bf88b-pmhz6 0/1 ContainerCreating 0 68s
kube-system pod/monitoring-influxdb-grafana-v4-6f74479987-rd5ck 0/2 ContainerCreating 0 68s
NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
default service/kubernetes ClusterIP 10.152.183.1 <none> 443/TCP 18h
kube-system service/heapster ClusterIP 10.152.183.195 <none> 80/TCP 68s
kube-system service/kubernetes-dashboard ClusterIP 10.152.183.171 <none> 443/TCP 68s
kube-system service/monitoring-grafana ClusterIP 10.152.183.120 <none> 80/TCP 68s
kube-system service/monitoring-influxdb ClusterIP 10.152.183.175 <none> 8083/TCP,8086/TCP 68s
NAMESPACE NAME READY UP-TO-DATE AVAILABLE AGE
kube-system deployment.apps/heapster-v1.5.2 0/1 1 0 68s
kube-system deployment.apps/kubernetes-dashboard 0/1 1 0 68s
kube-system deployment.apps/monitoring-influxdb-grafana-v4 0/1 1 0 68s
NAMESPACE NAME DESIRED CURRENT READY AGE
kube-system replicaset.apps/heapster-v1.5.2-c4dcfd9f8 1 1 0 68s
kube-system replicaset.apps/kubernetes-dashboard-c775bf88b 1 1 0 68s
kube-system replicaset.apps/monitoring-influxdb-grafana-v4-6f74479987 1 1 0 68s
Warning FailedCreatePodSandBox 2m26s (x3 over 2m54s) kubelet, mydnsname (combined from similar events): Failed create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox container: failed to create containerd task: failed to mount rootfs component &{overlay overlay [workdir=/var/snap/microk8s/common/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/1386/work upperdir=/var/snap/microk8s/common/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/1386/fs lowerdir=/var/snap/microk8s/common/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/2/fs]}: invalid argument: unknown
Warning MissingClusterDNS 2m14s (x13 over 4m58s) kubelet, mydnsname pod: "kubernetes-dashboard-c775bf88b-pmhz6_kube-system(777df7aa-d4de-40f0-8275-70b36d2e5029)". kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. Falling back to "Default" policy.
Filesystem Type Size Used Avail Use% Mounted on
none overlay 59G 21G 36G 37% /
tmpfs tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs tmpfs 743M 1.2M 742M 1% /run
tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs tmpfs 4.0M 0 4.0M 0% /sys/fs/cgroup
tmpfs tmpfs 372M 104K 372M 1% /run/user/1000