We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Error log.
k3d cluster create --agents 3 demo INFO[0000] Prep: Network INFO[0000] Created network 'k3d-demo' INFO[0000] Created image volume k3d-demo-images INFO[0000] Starting new tools node... INFO[0001] Creating node 'k3d-demo-server-0' INFO[0002] Pulling image 'ghcr.io/k3d-io/k3d-tools:5.4.6' INFO[0010] Pulling image 'docker.io/rancher/k3s:v1.24.4-k3s1' INFO[0059] Starting Node 'k3d-demo-tools' INFO[0294] Creating node 'k3d-demo-agent-0' INFO[0294] Creating node 'k3d-demo-agent-1' INFO[0295] Creating node 'k3d-demo-agent-2' INFO[0295] Creating LoadBalancer 'k3d-demo-serverlb' INFO[0297] Pulling image 'ghcr.io/k3d-io/k3d-proxy:5.4.6' INFO[0352] Using the k3d-tools node to gather environment information INFO[0353] HostIP: using network gateway 172.22.0.1 address INFO[0353] Starting cluster 'demo' INFO[0353] Starting servers... INFO[0354] Starting Node 'k3d-demo-server-0' WARN[0356] warning: encountered fatal log from node k3d-demo-server-0 (retrying 0/10): Mtime="2022-10-29T15:20:13Z" level=fatal msg="failed to find cpu cgroup (v2)" WARN[0359] warning: encountered fatal log from node k3d-demo-server-0 (retrying 1/10): Mtime="2022-10-29T15:20:15Z" level=fatal msg="failed to find cpu cgroup (v2)" WARN[0361] warning: encountered fatal log from node k3d-demo-server-0 (retrying 2/10): Mtime="2022-10-29T15:20:17Z" level=fatal msg="failed to find cpu cgroup (v2)" WARN[0363] warning: encountered fatal log from node k3d-demo-server-0 (retrying 3/10): Mtime="2022-10-29T15:20:19Z" level=fatal msg="failed to find cpu cgroup (v2)" WARN[0363] warning: encountered fatal log from node k3d-demo-server-0 (retrying 4/10): Mtime="2022-10-29T15:20:19Z" level=fatal msg="failed to find cpu cgroup (v2)" WARN[0365] warning: encountered fatal log from node k3d-demo-server-0 (retrying 5/10): Mtime="2022-10-29T15:20:21Z" level=fatal msg="failed to find cpu cgroup (v2)" WARN[0365] warning: encountered fatal log from node k3d-demo-server-0 (retrying 6/10): Mtime="2022-10-29T15:20:21Z" level=fatal msg="failed to find cpu cgroup (v2)" WARN[0366] warning: encountered fatal log from node k3d-demo-server-0 (retrying 7/10): Mtime="2022-10-29T15:20:21Z" level=fatal msg="failed to find cpu cgroup (v2)" WARN[0367] warning: encountered fatal log from node k3d-demo-server-0 (retrying 8/10): Mtime="2022-10-29T15:20:24Z" level=fatal msg="failed to find cpu cgroup (v2)" WARN[0368] warning: encountered fatal log from node k3d-demo-server-0 (retrying 9/10): Mtime="2022-10-29T15:20:24Z" level=fatal msg="failed to find cpu cgroup (v2)" ERRO[0368] Failed Cluster Start: Failed to start server k3d-demo-server-0: Node k3d-demo-server-0 failed to get ready: error waiting for log line `k3s is up and running` from node 'k3d-demo-server-0': stopped returning log lines: node k3d-demo-server-0 is running=true in status=restarting ERRO[0368] Failed to create cluster >>> Rolling Back INFO[0368] Deleting cluster 'demo' INFO[0369] Deleting cluster network 'k3d-demo' INFO[0369] Deleting 2 attached volumes... WARN[0369] Failed to delete volume 'k3d-demo-images' of cluster 'demo': failed to find volume 'k3d-demo-images': Error: No such volume: k3d-demo-images -> Try to delete it manually FATA[0369] Cluster creation FAILED, all changes have been rolled back!
Originally posted by @byteshiva in #1175
The text was updated successfully, but these errors were encountered:
k3d, works fine with root access.
I followed the steps listed below to make it work under non-root user.
https://rootlesscontaine.rs/getting-started/common/cgroup2/#enabling-cpu-cpuset-and-io-delegation
Refer: #1082
Sorry, something went wrong.
No branches or pull requests
Error log.
Originally posted by @byteshiva in #1175
The text was updated successfully, but these errors were encountered: