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

[release-1.24] bump runc to v1.1.5 #7177

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

[release-1.24] bump runc to v1.1.5 #7177

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

Comments

@brandond
Copy link
Member

@endawkins
Copy link

Validated on branch 1.24 with commit a6bd15f / version v1.24.12+k3s-a6bd15fb

Environment Details

Infrastructure

  • Cloud
  • Hosted

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

Linux ip-172-31-38-53 5.15.0-1026-aws #30-Ubuntu SMP Wed Nov 23 14:15:21 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
PRETTY_NAME="Ubuntu 22.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.1 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

Cluster Configuration:

1 server
1 agent

Config.yaml:

server node:
cluster-init: true
write-kubeconfig-mode: 644

agent node:
server: "https://<serverip>:6443"
token: secret

Additional files

none

Testing Steps

  1. Copy config.yaml
$ sudo mkdir -p /etc/rancher/k3s && sudo cp config.yaml /etc/rancher/k3s
  1. Install k3s
  2. Run the following command:
/var/lib/rancher/k3s/data/current/bin/runc --version

Replication Results:

  • k3s version used for replication:
k3s -v
k3s version v1.24.12+k3s1 (57e8adb5)
go version go1.19.7
server node:

/var/lib/rancher/k3s/data/current/bin/runc --version
runc version 1.1.4
commit: v1.1.4-0-g5fd4c4d
spec: 1.0.2-dev
go: go1.19.7
libseccomp: 2.5.4

agent:

/var/lib/rancher/k3s/data/current/bin/runc --version
runc version 1.1.4
commit: v1.1.4-0-g5fd4c4d
spec: 1.0.2-dev
go: go1.19.7
libseccomp: 2.5.4

Validation Results:

  • k3s version used for validation:
k3s -v
k3s version v1.24.12+k3s-a6bd15fb (a6bd15fb)
go version go1.19.7
Validating the Issue via Upgrade:

Commit Version: a6bd15fb71fb768416aefc17a9472b09fd1649af

curl -sfL https://get.k3s.io | sudo INSTALL_K3S_COMMIT=a6bd15fb71fb768416aefc17a9472b09fd1649af sh -

curl -sfL https://get.k3s.io | sudo INSTALL_K3S_COMMIT=a6bd15fb71fb768416aefc17a9472b09fd1649af sh -s - agent (Upgrade)

k3s -v
k3s version v1.24.12+k3s-a6bd15fb (a6bd15fb)
go version go1.19.7

server node:

/var/lib/rancher/k3s/data/current/bin/runc --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

agent:

/var/lib/rancher/k3s/data/current/bin/runc --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

Additional context / logs:

Validating the Issue via Clean Install:

server:

curl -sfL https://get.k3s.io | sudo INSTALL_K3S_COMMIT=a6bd15fb71fb768416aefc17a9472b09fd1649af sh -

agent:

curl -sfL https://get.k3s.io | sudo sudo K3S_URL=https://<serverip>:6443 INSTALL_K3S_COMMIT=a6bd15fb71fb768416aefc17a9472b09fd1649af INSTALL_K3S_TYPE="agent" K3S_TOKEN=secret sh -

k3s -v
k3s version v1.24.12+k3s-a6bd15fb (a6bd15fb)
go version go1.19.7

server:

/var/lib/rancher/k3s/data/current/bin/runc --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

agent:

/var/lib/rancher/k3s/data/current/bin/runc --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

@github-project-automation github-project-automation bot moved this from To Test to Done Issue in K3s Development Apr 12, 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