-
-
Notifications
You must be signed in to change notification settings - Fork 458
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
❗ Docker >=v20.10.5 (runc >= v1.0.0-rc93) is required for k3d v5.x ❗ #807
Comments
It doesn't happen anymore after upgrading from Docker 2.10.2 and containerd 1.4.3 to Docker 2.10.9 and containerd 1.4.11 |
Hey! I'm facing similar issue on Mac:
I have these installed and just upgraded with
Do you maybe have a suggestion on what to do? |
At first I downgraded k3d to 4.x and that fixed the problem but k3d 5.x with the newest docker/containerd versions also fixed it for me. |
Thanks, @manumartin ! Upgrading it with |
Hit the same issue on Ubuntu 18.0.4 with the same docker, containerd, and runc versions @franpog859 mentioned above. Upgraded docker via The resulting versions that worked for me:
|
I had the same exact problem, 4.x worked, upgrade to 5.x broke. As @tiswanso and others suggest, upgrading Docker fixed the issue. In case it helps - this is the version of Docker I was using on Ubuntu when in a broken state:
|
Hi @manumartin , thanks for opening this issue and thanks to the others for providing additional input and a "fix"/workaround. |
Tested some versions of Docker now with k3d v5.1.0 and I can confirm that it only starts working with Docker v20.10.4+ 🤔 |
@iwilltry42 -- in my case just documenting the version dependencies would have spared me a decent amount of effort. I'm just using k3d in an environment I completely control so updating dependencies is not much of a problem. Ideally, the k3d doc has a version compatibility matrix. |
@tiswanso , I'm definitely going to add a requirement for Docker >=v20.10.5. k3d x K3s I already had in CI/CD, which broke CI due to taking way to long to go through the E2E Tests with all K3s versions. Update: After some investigation, I feel like it's caused by runc (seems like the update v1.0.0-rc92...v1.0.0-rc93 fixed it) Update 2: Updated requirements on k3d.io and in the Readme: https://k3d.io/v5.1.0/#requirements |
Thanks for this issue, it saved me from a lot of debugging! I can report an occurrence of this issue on docker @iwilltry42 wouldn't it make more sense to clarify the requirement to "a docker version that uses
|
@schnatterer I didn't expect docker to ship the same exact version with a different version of runc to be honest. |
@iwilltry42 yeah, I was wondering about this myself. Thanks for updating. |
Following Arnold's recent recommendations, we've upgraded k3d to the latest 4.x release as the 5.x+ releases are not compatible with installed `runc` version. For more information please refer to: - openfun/arnold#733 - k3d-io/k3d#807 test docker executor rollback to the current ubuntu image Use the same circle version as Arnold Setup remote docker Upgrade k3d/kubectl releases restore machine executor Restore comment
Following Arnold's recent recommendations, we've upgraded k3d to the latest 4.x release as the 5.x+ releases are not compatible with installed `runc` version. For more information please refer to: - openfun/arnold#733 - k3d-io/k3d#807 test docker executor rollback to the current ubuntu image Use the same circle version as Arnold Setup remote docker Upgrade k3d/kubectl releases restore machine executor Restore comment
Following Arnold's recent recommendations, we've upgraded k3d to the latest 4.x release as the 5.x+ releases are not compatible with installed `runc` version. For more information please refer to: - openfun/arnold#733 - k3d-io/k3d#807 test docker executor rollback to the current ubuntu image Use the same circle version as Arnold Setup remote docker Upgrade k3d/kubectl releases restore machine executor Restore comment
Following Arnold's recent recommendations, we've upgraded k3d to the latest 4.x release as the 5.x+ releases are not compatible with installed `runc` version. For more information please refer to: - openfun/arnold#733 - k3d-io/k3d#807 test docker executor rollback to the current ubuntu image Use the same circle version as Arnold Setup remote docker Upgrade k3d/kubectl releases restore machine executor Restore comment
Sorry for bumping. Do I need to check the version of both Docker and runc, or just runc?
Not sure if it can run K3d. |
Hmm.. as far as I could tell, runc was the issue here, so that should be enough. |
A long time has passed and the reason for this was: k3d-io/k3d#807 We should be able to use the builtin runc instead Signed-off-by: Charly Molter <charly.molter@konghq.com>
) A long time has passed and the reason for this was: k3d-io/k3d#807 We should be able to use the builtin runc instead --------- Signed-off-by: Charly Molter <charly.molter@konghq.com> Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
❗ TL;DR: Docker >=v20.10.5 is required for k3d v5.x ❗
What did you do
I tried to create a k3d cluster with k3d 5.x but it fails. Its working with 4.x
How was the cluster created?
sudo k3d cluster create MYCLUSTER --trace --verbose
What did you do afterwards?
It seems like some kind of k3d/docker integration issue. I have reproduced the error message by using this docker-compose.yml:
It seems you can't mount the docker sock volume inside the /var/run tmpfs mount and k3d is failing when trying to do the same with the k3d-tools container.
What did you expect to happen
I expected the cluster to start normally
Screenshots or terminal output
Which OS & Architecture
Which version of
k3d
k3d version v5.0.1
k3s version v1.21.5-k3s1 (default)`
Which version of docker
Client: Docker Engine - Community Version: 20.10.2 API version: 1.41 Go version: go1.13.15 Git commit: 2291f61 Built: Mon Dec 28 16:17:32 2020 OS/Arch: linux/amd64 Context: default Experimental: true
The text was updated successfully, but these errors were encountered: