-
-
Notifications
You must be signed in to change notification settings - Fork 452
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
[BUG] k3d v5.1.0 not starting on Docker 20.10.11 #873
Comments
Hi @applike-ss , thanks for opening this issue! �[37mTRAC�[0m[0001] NodeWaitForLogMessage: Node 'k3d-k3s-default-server-0' waiting for log message 'k3s is up and running' since '2021-11-30 11:31:51 +0000 UTC'
�[36mINFO�[0m[0003] Deleting cluster 'k3s-default' Where the hell does this jump from "creating" to "deleting" come from? I cannot see a way this could happen without any error/fatal log message 🤔 I'm on the exact same Kernel, Docker Client/Server, k3d/K3s versions on Ubuntu (PopOS), without any problems 🤔 |
@iwilltry42 I submitted the complete log, nothings stripped out or so. Yeah i had a "not starting up" issue with the k3d version 4 as well and since i wanted to try some stuff out on a temporary k8s cluster, i though i'd try the update and check if that works. Now with it not working (and me getting more devops work recently), it would be nice to get it working somehow. Is there anything i can try out or information that i could forward to you? |
So I'm really lost here. There's no indication of failure, k3d doesn't log anything about its intention to rollback, there's no Can you maybe try again with |
i just checked again and my output redirection was broken. I updated the logs in the first post. SORRY!!! |
Ah now that makes some more sense 😁 |
These are the logs:
|
Ah, well there we go: EDIT: Actually I could've seen this from your WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
WARNING: No cpu shares support EDIT 2: In your case it's probably related to this: https://github.com/xanmod/linux/issues/3 |
Thanks for your help! I wonder if that is still up-to-date because xanmod has moved from cacule to the task type scheduler. Will try it anyway and let you know :) |
I booted with swapaccount=1, but still get the three warnings that you mentioned from docker info - and k3d still doesn't start (obviously for the same reasons).
EDIT: The workaround mentioned first also didn't work |
I'm also affected by this.
Looks like I picked the wrong day to update docker... |
The solution for me was to switch to the linux-xanmod kernel package which uses CFS, so i don't have cacule/tt scheduler now - but k3d is working nicely so far :-) |
What did you do
How was the cluster created?
k3d cluster create
(output appended was generated with--trace
)What did you do afterwards?
What did you expect to happen
Cluster should come up and be usable
Screenshots or terminal output
Which OS & Architecture
Which version of
k3d
Which version of docker
output of
docker version
:and
docker info
:The text was updated successfully, but these errors were encountered: