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 runc to v1.1.5 #7175

Closed
brandond opened this issue Mar 29, 2023 · 1 comment
Closed

bump runc to v1.1.5 #7175

brandond opened this issue Mar 29, 2023 · 1 comment
Assignees
Milestone

Comments

@brandond
Copy link
Member

runc v1.1.5 is out and fixes some vulnerabilities. We should use it.

@brandond brandond self-assigned this Mar 29, 2023
@brandond brandond added this to the v1.26.4+k3s1 milestone Mar 29, 2023
@brandond brandond moved this to Peer Review in K3s Development Mar 29, 2023
@brandond brandond moved this from Peer Review to To Test in K3s Development Apr 5, 2023
@fmoral2
Copy link
Contributor

fmoral2 commented Apr 11, 2023

Validated on Version: From master

Environment Details

Infrastructure
Cloud EC2 instance

Node(s) CPU architecture, OS, and Version:
Ubuntu 20.04

Cluster Configuration:
1 node

Config.yaml 1 node :

cat /etc/rancher/k3s/config.yaml
write-kubeconfig-mode: 644
token: <>

Steps to validate the fix:

  1. Copy config.yaml
  2. Install k3s with commit ID from master
  3. Check runc version
  4. Check if can deploy a pod and its everything working fine

Validation Results:

             
                       
k3s version v1.26.3+k3s-877247a6 (877247a6) COMMIT ID= (877247a6911c09ccc26b72415a6326e9646d88bd)


~$ k3s --version
k3s version v1.26.3+k3s-877247a6 (877247a6)
go version go1.19.7

~$ RUNC_PATH=$(find /var/lib/rancher/k3s/data/ -type f -name "runc" | head -1)
~$ sudo $RUNC_PATH --version
runc version 1.1.5
commit: v1.1.5-0-gf19387a
spec: 1.0.2-dev
go: go1.19.7
libseccomp: 2.5.4


~$ k apply -f dep.yaml 

~$ kubectl get pod busybox-test -o wide
NAME           READY   STATUS    RESTARTS   AGE   IP          NODE               NOMINATED NODE   READINESS GATES
busybox-test   1/1     Running   0          21s   10.42.0.9   ip-172-31-37-172   <none>           <none>





@fmoral2 fmoral2 closed this as completed Apr 11, 2023
@github-project-automation github-project-automation bot moved this from To Test to Done Issue in K3s Development Apr 11, 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