Replies: 1 comment
-
For anyone who runs across this, it should execute pretty quick, if not something is likely wrong. I had a similar issue, though, where it would sit there for hours. You can try checking I'm running a RHEL 9.5 machine, and the docker logs gave me the specific error "failed to find cpu cgroup (v2)". I fixed my errors by reverting to cgroup version 1 and making sure docker was using the default context (i.e. not rootless). Some resources I found helpful for RedHat: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone:
I'm trying to use k3d to create a cluster and it doesn't seem to want to work for me. How long does it take for you to do it? Minutes? Hours? After installing docker, kubectl, and k3d, if I run the command:
k3d cluster create mycluster --api-port 6443 --servers 1 --agents 1 -p 30000-32767:30000-32767@server:0
it makes it to INFO[0026] Starting Node 'k3d-portainer-agent-0' and just sits there. How long does it take?
I've also tried the following command:
k3d cluster create mycluster --api-port 6443 --servers 1 --agents 1 -p 30000:30000@server:0
and I seem to be having the same problem.
What do you think? Should I just let it run all night? or is there something wrong somewhere?
Thanks in advance for your time/replies.
Beta Was this translation helpful? Give feedback.
All reactions