Skip to content
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] Error response from daemon: cgroups: cannot find cgroup mount destination #240

Closed
evillgenius75 opened this issue May 13, 2020 · 2 comments
Labels
bug Something isn't working runtime Issue with the container runtime (docker)

Comments

@evillgenius75
Copy link

Describe what you did leading up to the issue

  • How was the cluster created?

    • k3d create cluster mycluster
  • What did you do afterwards?

    • k3d commands?
    • docker commands?
    • OS operations (e.g. shutdown/reboot)?

docker ps -a shows nothing
docker image ls shows: rancher/k3s v1.17.4-k3s1 d080d71a66ab 7 weeks ago 147MB
I reran k3d create cluster mycluster with the --verbose flag and output is:

DEBU[0000] Selected runtime is 'docker.Docker'
DEBU[0000] map[]
INFO[0000] Created network 'k3d-mycluster'
INFO[0000] Created volume 'k3d-mycluster-images'
INFO[0001] Creating node 'k3d-mycluster-master-0'
DEBU[0001] Creating node from spec
&{Name:k3d-mycluster-master-0 Role:master Image:docker.io/rancher/k3s:v1.17.4-k3s1 Volumes:[k3d-mycluster-images:/k3d/images] Env:[K3S_TOKEN=gZLhEJrjERJeOKeglssn] Cmd:[] Args:[] Ports:[] Restart:false Labels:map[k3d.cluster:mycluster k3d.cluster.imageVolume:k3d-mycluster-images k3d.cluster.network:8dac1df0ec2fcca46220d3e17097e7192ebe556348591de1bc4d6dd1f6a5c277 k3d.cluster.network.external:false k3d.cluster.secret:gZLhEJrjERJeOKeglssn] Network:8dac1df0ec2fcca46220d3e17097e7192ebe556348591de1bc4d6dd1f6a5c277 MasterOpts:{IsInit:false ExposeAPI:{Host:0.0.0.0 HostIP:0.0.0.0 Port:6443}} WorkerOpts:{}}
DEBU[0001] spec = &{Name:k3d-mycluster-master-0 Role:master Image:docker.io/rancher/k3s:v1.17.4-k3s1 Volumes:[k3d-mycluster-images:/k3d/images] Env:[K3S_TOKEN=gZLhEJrjERJeOKeglssn K3S_KUBECONFIG_OUTPUT=/output/kubeconfig.yaml] Cmd:[] Args:[server --tls-san 0.0.0.0] Ports:[] Restart:false Labels:map[app:k3d k3d.cluster:mycluster k3d.cluster.imageVolume:k3d-mycluster-images k3d.cluster.network:8dac1df0ec2fcca46220d3e17097e7192ebe556348591de1bc4d6dd1f6a5c277 k3d.cluster.network.external:false k3d.cluster.secret:gZLhEJrjERJeOKeglssn k3d.master.api.host:0.0.0.0 k3d.master.api.hostIP:0.0.0.0 k3d.master.api.port:6443 k3d.role:master] Network:8dac1df0ec2fcca46220d3e17097e7192ebe556348591de1bc4d6dd1f6a5c277 MasterOpts:{IsInit:false ExposeAPI:{Host:0.0.0.0 HostIP:0.0.0.0 Port:6443}} WorkerOpts:{}}
DEBU[0001] docker.CreateNode...
DEBU[0001] Creating docker container with translated config
&{ContainerConfig:{Hostname:k3d-mycluster-master-0 Domainname: User: AttachStdin:false AttachStdout:false AttachStderr:false ExposedPorts:map[] Tty:false OpenStdin:false StdinOnce:false Env:[K3S_TOKEN=gZLhEJrjERJeOKeglssn K3S_KUBECONFIG_OUTPUT=/output/kubeconfig.yaml] Cmd:[server --tls-san 0.0.0.0] Healthcheck:<nil> ArgsEscaped:false Image:docker.io/rancher/k3s:v1.17.4-k3s1 Volumes:map[] WorkingDir: Entrypoint:[] NetworkDisabled:false MacAddress: OnBuild:[] Labels:map[app:k3d k3d.cluster:mycluster k3d.cluster.imageVolume:k3d-mycluster-images k3d.cluster.network:8dac1df0ec2fcca46220d3e17097e7192ebe556348591de1bc4d6dd1f6a5c277 k3d.cluster.network.external:false k3d.cluster.secret:gZLhEJrjERJeOKeglssn k3d.master.api.host:0.0.0.0 k3d.master.api.hostIP:0.0.0.0 k3d.master.api.port:6443 k3d.role:master] StopSignal: StopTimeout:<nil> Shell:[]} HostConfig:{Binds:[k3d-mycluster-images:/k3d/images] ContainerIDFile: LogConfig:{Type: Config:map[]} NetworkMode: PortBindings:map[] RestartPolicy:{Name: MaximumRetryCount:0} AutoRemove:false VolumeDriver: VolumesFrom:[] CapAdd:[] CapDrop:[] Capabilities:[] CgroupnsMode: DNS:[] DNSOptions:[] DNSSearch:[] ExtraHosts:[] GroupAdd:[] IpcMode: Cgroup: Links:[] OomScoreAdj:0 PidMode: Privileged:true PublishAllPorts:false ReadonlyRootfs:false SecurityOpt:[] StorageOpt:map[] Tmpfs:map[/run: /var/run:] UTSMode: UsernsMode: ShmSize:0 Sysctls:map[] Runtime: ConsoleSize:[0 0] Isolation: Resources:{CPUShares:0 Memory:0 NanoCPUs:0 CgroupParent: BlkioWeight:0 BlkioWeightDevice:[] BlkioDeviceReadBps:[] BlkioDeviceWriteBps:[] BlkioDeviceReadIOps:[] BlkioDeviceWriteIOps:[] CPUPeriod:0 CPUQuota:0 CPURealtimePeriod:0 CPURealtimeRuntime:0 CpusetCpus: CpusetMems: Devices:[] DeviceCgroupRules:[] DeviceRequests:[] KernelMemory:0 KernelMemoryTCP:0 MemoryReservation:0 MemorySwap:0 MemorySwappiness:<nil> OomKillDisable:<nil> PidsLimit:<nil> Ulimits:[] CPUCount:0 CPUPercent:0 IOMaximumIOps:0 IOMaximumBandwidth:0} Mounts:[] MaskedPaths:[] ReadonlyPaths:[] Init:<nil>} NetworkingConfig:{EndpointsConfig:map[8dac1df0ec2fcca46220d3e17097e7192ebe556348591de1bc4d6dd1f6a5c277:0xc000444000]}}
DEBU[0001] Created container 6b14c3c246fb6a1344eec9197fc6cb30e9751478a4be560ca87ac1fd4943c334
ERRO[0001] Failed to start container
ERRO[0001] Failed to create k3d node
ERRO[0001] Failed to create node
ERRO[0001] Error response from daemon: cgroups: cannot find cgroup mount destination: unknown
ERRO[0001] Failed to create cluster >>> Rolling Back
INFO[0001] Deleting cluster 'mycluster'
DEBU[0001] &{Name:mycluster Network:{Name:8dac1df0ec2fcca46220d3e17097e7192ebe556348591de1bc4d6dd1f6a5c277 External:false} Secret:gZLhEJrjERJeOKeglssn Nodes:[0xc00039f320] InitNode:<nil> ExternalDatastore:{Endpoint: CAFile: CertFile: KeyFile: Network:} CreateClusterOpts:0xc00031b8c0 ExposeAPI:{Host:0.0.0.0 HostIP:0.0.0.0 Port:6443} ImageVolume:}
DEBU[0001] docker.DeleteNode...
INFO[0001] Deleted k3d-mycluster-master-0
INFO[0001] Deleting cluster network '8dac1df0ec2fcca46220d3e17097e7192ebe556348591de1bc4d6dd1f6a5c277'
FATA[0002] Cluster creation FAILED, all changes have been rolled back!

Describe what you expected to happen

Concise description of what you expected to happen after doing what you described above.

Add screenshots or terminal output

Cluster never builds. Image is pulled and then immediately errors.

INFO[0000] Created network 'k3d-mycluster'
INFO[0000] Created volume 'k3d-mycluster-images'
INFO[0001] Creating node 'k3d-mycluster-master-0'
INFO[0002] Pulling image 'docker.io/rancher/k3s:v1.17.4-k3s1'
ERRO[0022] Failed to start container
ERRO[0022] Failed to create k3d node
ERRO[0022] Failed to create node
ERRO[0022] Error response from daemon: cgroups: cannot find cgroup mount destination: unknown
ERRO[0022] Failed to create cluster >>> Rolling Back
INFO[0022] Deleting cluster 'mycluster'
INFO[0022] Deleted k3d-mycluster-master-0
INFO[0022] Deleting cluster network 'de77a82f42b48629cab5a9433b598eb0c78bfa29cd4c3345e7a7c29c87970ff6'
FATA[0022] Cluster creation FAILED, all changes have been rolled back!

Describe your Setup

Docker running native in WSL2 running ubuntu 18.04

OS / Architecture

  • Linux, Windows, MacOS / amd64, x86, ...?

k3d version

  • k3d version v3.0.0-beta.0

docker version

  • output of docker version
Client: Docker Engine - Community
 Version:           19.03.8
 API version:       1.40
 Go version:        go1.12.17
 Git commit:        afacb8b7f0
 Built:             Wed Mar 11 01:25:46 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.8
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.17
  Git commit:       afacb8b7f0
  Built:            Wed Mar 11 01:24:19 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683
@evillgenius75 evillgenius75 added the bug Something isn't working label May 13, 2020
@iwilltry42 iwilltry42 added the runtime Issue with the container runtime (docker) label May 14, 2020
@iwilltry42
Copy link
Member

Hi @evillgenius75, thanks for opening this issue and testing the v3 Beta :)
This sounds like a runtime issue, which cannot be fixed on k3d side.
Google turned this up: microsoft/WSL#4189 which seems to be the sam/a similar issue. An there's a fix in/workaround in the comments.

@evillgenius75
Copy link
Author

Thank you @iwilltry42 you were spot on! Got my cluster running with that "fix"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working runtime Issue with the container runtime (docker)
Projects
None yet
Development

No branches or pull requests

2 participants