-
-
Notifications
You must be signed in to change notification settings - Fork 455
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] New Cluster stuck on ContainerCreating #1449
Comments
fwiw, I'm seeing this same issue starting today. |
In my case, this was solved by disconnecting from my VPN. The docker container logs pointed me toward a networking issue, which it seems to be for me. |
Yeah, it's not a network issue for me as I've experienced this on two devices. Just simply rolling back seems to work without other changes so it's difficult to work out this issue. I've had a look at changing the k3s rancher image to see if this helps but no changes in behaviour. K3d 5.6.3 seems to something strange about how it's mapping DNS in the container. |
Same here. 5.6.0 works but 5.6.2 does not (nor does 5.6.3). It seems to be using the wrong nameserver in /etc/resolv.conf inside the k3d container:
Rolling back to 5.6.0 (note how the nameserver is rewritten to 127.0.0.11):
|
Fixed for me by disabling the dns fix when creating the cluster: |
@adriaanm - This workaround suggested seems to have worked.
It would be good if was documented somewhere. |
Hi, have a look at #1445, that might describe the reason why the use of |
What did you do
How was the cluster created?
k3d cluster create mycluster
What did you do afterwards?
What did you expect to happen
I was expecting a deploy of nginx to be started and ready for consumption however upon investigation is appears that
mycluster
does not appear to start correctly as pods stuck in acontainercreating
state, they seem to be failing to pull down container images.NOTE: This issue DOES NOT OCCUR when using K3d 5.6.0, as I have rolled back to this version and the cluster bootstraps fine.
Screenshots or terminal output
Which OS & Architecture
k3d runtime-info
Which version of
k3d
k3d version
Which version of docker
docker version
anddocker info
The text was updated successfully, but these errors were encountered: