-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Repeated "failed to fetch hugetlb info" error from runc on Raspberry Pi #4580
Comments
Start-up logs. Sorry it's a lot of output
|
You have lots of "hugetlb" mentions here, which may be related to #3517 |
and that issue references opencontainers/runc#3232 which may be worth a second look |
Here's the k3s config check:
|
May be related to #3897 |
@dweomer I'm happy to keep my RPi around until a fix is available here or upstream for the Raspberry Pi distro. |
Looks like we'll need to update to runc 1.0.3 when it comes out: opencontainers/runc#3295 |
Until then @alexellis you might see if the workaround from #4234 (comment) solves this for you? |
The referenced solution suggests to install a package only available for Ubuntu, but the original poster and I are both running Raspberry Pi OS (a Debian-based distro) in which said package does not exist. The issue was |
Using commit id ** ** from master branch, having runc version 1.0.3 "failed to fetch hugetlb info" error from runc is not seen in logs
|
I'm seeing lots of errors with K3s and Raspberry Pi Bullseye. K3s does start and kubectl does respond.
Environmental Info:
K3s Version:
Node(s) CPU architecture, OS, and Version:
Cluster Configuration:
Describe the bug:
Can the errors be resolved?
Steps To Reproduce:
Expected behavior:
No errors
Actual behavior:
See below
Additional context / logs:
The text was updated successfully, but these errors were encountered: