Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump containerd to v1.7.3 / runc v1.1.8 #7986

Closed
brandond opened this issue Jul 14, 2023 · 1 comment
Closed

Bump containerd to v1.7.3 / runc v1.1.8 #7986

brandond opened this issue Jul 14, 2023 · 1 comment
Assignees
Milestone

Comments

@brandond
Copy link
Member

brandond commented Jul 14, 2023

There is a new release of containerd available; we should update. We should update runc at the same time.

@brandond brandond moved this from New to Next Up in K3s Development Jul 14, 2023
@brandond brandond added this to the v1.27.5+k3s1 milestone Jul 14, 2023
@brandond brandond assigned brandond and unassigned brandond Jul 14, 2023
@brandond brandond changed the title Bump containerd to v1.7.2 Bump containerd to v1.7.3 / runc v1.1.8 Aug 2, 2023
@brandond brandond moved this from Next Up to Peer Review in K3s Development Aug 2, 2023
@VestigeJ VestigeJ moved this from Peer Review to Needs Additional in K3s Development Aug 11, 2023
@VestigeJ
Copy link

##Environment Details
VERSION=v1.27.4+k3s1
validated on VERSION=v1.27.5-rc1+k3s1

Infrastructure

  • Cloud

Node(s) CPU architecture, OS, and version:

ami-0bbc06589f2e4f4f2

Linux 5.14.21-150500.53-default x86_64 GNU/Linux

PRETTY_NAME="SUSE Linux Enterprise Server 15 SP5"

Cluster Configuration:

NAME STATUS ROLES AGE VERSION
ip-12-1-22-137 Ready control-plane,etcd,master 18m v1.27.5-rc1+k3s1

Config.yaml:

write-kubeconfig-mode: 644
debug: true
token: YOUR_TOKEN_HERE
protect-kernel-defaults: true
cluster-init: true

Reproduction

$ curl https://get.k3s.io --output install-"k3s".sh
$ sudo chmod +x install-"k3s".sh
$ sudo groupadd --system etcd && sudo useradd -s /sbin/nologin --system -g etcd etcd
$ sudo modprobe ip_vs_rr
$ sudo modprobe ip_vs_wrr
$ sudo modprobe ip_vs_sh
$ sudo printf "on_oovm.panic_on_oom=0 \nvm.overcommit_memory=1 \nkernel.panic=10 \nkernel.panic_ps=1 \nkernel.panic_on_oops=1 \n" > ~/90-kubelet.conf
$ sudo cp 90-kubelet.conf /etc/sysctl.d/
$ sudo systemctl restart systemd-sysctl
$ sudo INSTALL_K3S_VERSION=v1.27.4+k3s1 INSTALL_K3S_EXEC=server ./install-k3s.sh
$ set_kubefig //export KUBECONFIG=/etc/rancher/k3s/k3s.yaml
$ kgp -A //kubectl get pods -A
$ /var/lib/rancher/k3s/data/current/bin/runc -v

Results:

$ /var/lib/rancher/k3s/data/current/bin/runc -v

runc version 1.1.7
commit: v1.1.7-0-g860f061
spec: 1.0.2-dev
go: go1.20.6
libseccomp: 2.5.4

Validation

$ curl https://get.k3s.io --output install-"k3s".sh
$ sudo chmod +x install-"k3s".sh
$ sudo groupadd --system etcd && sudo useradd -s /sbin/nologin --system -g etcd etcd
$ sudo modprobe ip_vs_rr
$ sudo modprobe ip_vs_wrr
$ sudo modprobe ip_vs_sh
$ sudo printf "on_oovm.panic_on_oom=0 \nvm.overcommit_memory=1 \nkernel.panic=10 \nkernel.panic_ps=1 \nkernel.panic_on_oops=1 \n" > ~/90-kubelet.conf
$ sudo cp 90-kubelet.conf /etc/sysctl.d/
$ sudo systemctl restart systemd-sysctl
$ sudo INSTALL_K3S_VERSION=v1.27.5-rc1+k3s1 INSTALL_K3S_EXEC=server ./install-k3s.sh
$ kgp -A //kubectl get pods -A
$ /var/lib/rancher/k3s/data/current/bin/runc -v
$ k3s -v 

Results:

$ /var/lib/rancher/k3s/data/current/bin/runc -v

runc version 1.1.8
commit: v1.1.8-0-g82f18fe
spec: 1.0.2-dev
go: go1.20.7
libseccomp: 2.5.4

@github-project-automation github-project-automation bot moved this from Needs Additional to Done Issue in K3s Development Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants