2.6.升级 containerd-北京尧图网络

更新前/usr/local/bin/下的 containerd 相关文件# ll /usr/local/bin/ total 279M lrwxrwxrwx 1 root root 33 Jul 14 2025 nerdctl - /usr/local/containerd/bin/nerdctl -rwxr-xr-x 1 demo demo 23M Mar 28 2025 etcd -rwxr-xr-x 1 demo demo 18M Mar 28 2025 etcdctl -rwxr-xr-x 1 root root 27M Mar 18 2025 ctd-decoder -rwxr-xr-x 1 root root 55M Mar 18 2025 crictl -rwxr-xr-x 1 root root 56M Mar 18 2025 critest -rwxr-xr-x 1 root root 39M Mar 18 2025 containerd -rwxr-xr-x 1 root root 6.4M Mar 18 2025 containerd-shim -rwxr-xr-x 1 root root 7.4M Mar 18 2025 containerd-shim-runc-v1 -rwxr-xr-x 1 root root 13M Mar 18 2025 containerd-shim-runc-v2 -rwxr-xr-x 1 root root 18M Mar 18 2025 containerd-stress -rwxr-xr-x 1 root root 19M Mar 18 2025 ctr解压新版本--strip-components1去掉压缩包内的bin/目录层级直接覆盖到/usr/local/bin/# tar tf containerd-2.3.2-linux-amd64.tar.gz bin/ bin/containerd bin/containerd-shim-runc-v2 bin/ctr bin/containerd-stress # tar -xzvf containerd-2.3.2-linux-amd64.tar.gz --strip-components1 -C /usr/local/bin/更新后containerd 主程序及相关组件更新为Jun 19时间戳注意旧版的containerd-shim、containerd-shim-runc-v1等 2.0 已废弃的 shim 仍保留但不再使用# ll /usr/local/bin/ total 286M -rwxr-xr-x 1 root root 42M Jun 19 07:14 containerd -rwxr-xr-x 1 root root 8.1M Jun 19 07:14 containerd-shim-runc-v2 -rwxr-xr-x 1 root root 22M Jun 19 07:14 containerd-stress -rwxr-xr-x 1 root root 25M Jun 19 07:14 ctr lrwxrwxrwx 1 root root 33 Jul 14 2025 nerdctl - /usr/local/containerd/bin/nerdctl -rwxr-xr-x 1 demo demo 23M Mar 28 2025 etcd -rwxr-xr-x 1 demo demo 18M Mar 28 2025 etcdctl -rwxr-xr-x 1 root root 27M Mar 18 2025 ctd-decoder -rwxr-xr-x 1 root root 55M Mar 18 2025 crictl -rwxr-xr-x 1 root root 56M Mar 18 2025 critest # 2.0 已废弃 -rwxr-xr-x 1 root root 6.4M Mar 18 2025 containerd-shim # 2.0 已废弃 -rwxr-xr-x 1 root root 7.4M Mar 18 2025 containerd-shim-runc-v12.7.重启 containerd 并验证systemctl restart containerd systemctl status containerd3.验证升级结果逐节点升级完成后确认运行时版本已更新为containerd://2.3.2# kubectl get node -o wide NAME STATUS ROLES AGE VERSION INTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME x.x.x Ready control-plane 344d v1.35.6 x.x.x.x Ubuntu 24.04.4 LTS 6.8.0-124-generic containerd://2.3.2 x.x.x Ready control-plane 344d v1.35.6 x.x.x.x Ubuntu 24.04.4 LTS 6.8.0-124-generic containerd://2.3.2 x.x.x Ready control-plane 344d v1.35.6 x.x.x.x Ubuntu 24.04.4 LTS 6.8.0-124-generic containerd://2.3.2问题处理1.Kubernetes 问题处理1.1.基础镜像版本不一致问题原因新版 kubeadm 默认使用的 pause 镜像版本与节点上 containerd 配置的不一致。表现形式在执行 kubeadm upgrade apply 时可能会出现基础镜像不一致的告警detected that the sandbox image registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.8 of the container runtime is inconsistent with that used by kubeadm. It is recommended to use registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.10 as the CRI sandbox image.解决方式查看当前 kubeadm 期望的镜像版本# kubeadm config images list # 此处报错是由于无法连接 https://dl.k8s.io/release/stable-1.txt,但不影响输出所需镜像 W0626 10:30:12.306990 2755682 version.go:108] could not fetch a Kubernetes version from the internet: unable to get URL https://dl.k8s.io/release/stable-1.txt: Get https://dl.k8s.io/release/stable-1.txt: context deadline exceeded (Client.Timeout exceeded while awaiting headers) W0626 10:30:12.307154 2755682 version.go:109] falling back to the local client version: v1.35.6 registry.k8s.io/kube-apiserver:v1.35.6 registry.k8s.io/kube-controller-manager:v1.35.6 registry.k8s.io/kube-scheduler:v1.35.6 registry.k8s.io/kube-proxy:v1.35.6 registry.k8s.io/coredns/coredns:v1.13.1 registry.k8s.io/pause:3.10.1 registry.k8s.io/etcd:3.6.6-0 # 查看当前 containerd 实际配置 grep -i pause: /etc/containerd/config.toml sandbox_image registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.8把 containerd 配置中的 pause 版本更新到提示的新版本然后重启 containerd 即可sed -i s#pause:3.8#pause:3.10.1# /etc/containerd/config.toml systemctl restart containerd1.2.集群更新使用的版本格式问题问题原因升级时kubeadm upgrade apply所用版本不是 K8s 版本号表现形式升级时提示版本无效# kubeadm upgrade apply 1.33.13-1.1 error execution phase preflight: the version argument is invalid due to these errors: - Specified version to upgrade to v1.33.13-1.1 is an unstable version and such upgrades werent allowed via setting the --allow-*-upgrades flags Can be bypassed if you pass the --force flag解决方式kubeadm upgrade apply所用的版本必须是K8s 版本号如1.33.13而不是 apt 包的 Ubuntu 格式如1.33.13-1.1# kubeadm upgrade apply 1.33.131.3.集群配置中 controlPlaneEndpoint 与实际 bindPort 不一致问题原因这个告警无需在意它只是提示controlPlaneEndpoint覆盖了bindPort。本集群用 HAProxy 做负载均衡前端监听16443再转发给后端 kube-apiserver 的6443所以这个覆盖正是预期行为。表现形式升级过程中 kubeadm upgrade 输出WARNING: port specified in controlPlaneEndpoint overrides bindPort in the controlplane address解决方式符合预期即可无需解决# ss -nltup | grep 6443 tcp LISTEN 0 2000 0.0.0.0:16443 0.0.0.0:* users:((haproxy,pid1892947,fd10)) tcp LISTEN 0 2000 127.0.0.1:16443 0.0.0.0:* users:((haproxy,pid1892947,fd11)) tcp LISTEN 0 16384 *:6443 *:* users:((kube-apiserver,pid1697748,fd4)) # kubectl -n kube-system get cm kubeadm-config -o yaml | grep -i controlPlaneEndpoint controlPlaneEndpoint: 10.51.0.249:16443 # cat /etc/haproxy/haproxy.cfg global maxconn 2000 ulimit-n 16384 log 127.0.0.1 local0 err stats timeout 30s defaults log global mode http option httplog timeout connect 5000 timeout client 50000 timeout server 50000 timeout http-request 15s timeout http-keep-alive 15s frontend monitor-in bind *:33305 mode http option httplog monitor-uri /monitor frontend k8s-master bind 0.0.0.0:16443 bind 127.0.0.1:16443 mode tcp option tcplog tcp-request inspect-delay 5s default_backend k8s-master backend k8s-master mode tcp option tcplog option tcp-check balance roundrobin default-server inter 10s downinter 5s rise 2 fall 2 slowstart 60s maxconn 250 maxqueue 256 weight 100 server x.x.x x.x.x.x:6443 check server x.x.x x.x.x.x:6443 check server x.x.x x.x.x.x:6443 check1.4.集群更新使用的 containerd 版本过旧问题原因使用的 containerd 版本较旧K8s 1.36 版本后会删除从 kubelet 配置读 cgroupDriver 这个老机制fallback改用 CRI 的RuntimeConfig方法从 containerd 直接探测。但当前 containerd 1.7 不支持这个新方法所以出现警告。根据官网说明在 K8s 1.38 版本前完成 containerd 升级即可。表现形式在v1.34.x升级到v1.35.x时kubeadm 输出ContainerRuntimeVersion告警# kubeadm upgrade apply 1.35.6 [upgrade/preflight] Running preflight checks [WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet config will be removed in 1.36. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri解决方式升级 containerd 版本即可2.Containerd 问题处理

2.6.升级 containerd

相关推荐

影刀RPA新手教程：界面布局完全指南——指令区、画布区、属性区深度解析与使用技巧

LangChain使用deep agent并且加载SKILL

LLM嵌入运动规划内核：语义约束自动转数学表达

更多资讯

分布式对象存储系统设计与性能优化实践

LaTeX脚注设置全解析：编号、版式与特殊环境排错指南

Kafka核心价值与大数据应用实战解析

百度文库文档免费下载技术方案全解析

RFID射频识别技术试卷：命题逻辑、答题主线与工程能力分层

Agent记忆不跟工具搬家：分层设计与跨框架迁移实战

今日更新

PLFM_RADAR：从被动告警到主动感知的微服务健康监控系统

SPI隔离设计实战：MAX14431BAEE+与STM32F407工业级应用

数字隔离器如何根治SPI通信地环路干扰：MAX14431与TM4C129实战

本周精选

面向复杂光照与角度的宠物面部识别鲁棒性增强策略

基于DRV8818与STM32的双极步进电机驱动方案实战解析

DRV8818PWPR+PIC18F45K80双极步进电机控制方案实战

本月热门

面向复杂光照与角度的宠物面部识别鲁棒性增强策略

基于DRV8818与STM32的双极步进电机驱动方案实战解析

DRV8818PWPR+PIC18F45K80双极步进电机控制方案实战

读完文章，想聊聊您的网站？