May 27, 20242 yr I've been getting the following error when trying to create new docker containers. docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: unable to apply cgroup configuration: mkdir /sys/fs/cgroup/docker/d28306ef84f9d638e08015a84f6a8183cf39bf2d1d799b48296ac49c3227d1d1: no space left on device: unknown. I did find this post but it didn't solve the problem
May 27, 20242 yr Community Expert Try re-creating the docker image: https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks If that doesn't help post the diagnostics.
June 9, 20242 yr Author I've tried recreating the docker image and I'm not using custom docker networks. I'm still getting the error. The link to capture the diagnostics is pointing to recreating a password. I just clicked on the Diagnostics in Tools and downloaded it. Hopefully this is what you're looking for. longhaul-diagnostics-20240609-1308.zip
June 9, 20242 yr Community Expert Log is full of spam, cannot even see any docker related messages, but I see in the confirm that you are using a docker folder, switch to image, if the same reboot to clear the logs and post new diags after array start.
January 26, 20251 yr I have the same. Observed this 2 times with some month in between. But something seems not right. I have no image, I have a docker directory set. There IS space available, so no clue what the issue. 6.12.14. docker start urbackup-ncbackup Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: unable to apply cgroup configuration: mkdir /sys/fs/cgroup/docker/32089c8491bddd232588f4567a6c0320bc3e88090aa2eab98faf1befc2589331: no space left on device: unknown Error: failed to start containers: urbackup-ncbackup Any ideas? This docker start error is not being logged into the syslog as I see. Dont know why.
January 26, 20251 yr Community Expert Recommend changing to a docker image, docker folder sometimes causes strange issues.
January 26, 20251 yr Is that noted in the docs? With any reasons? If its like this, I try switching back to an image.
January 26, 20251 yr Community Expert 3 hours ago, KluthR said: Is that noted in the docs? No, observation is based mostly on my experience in the forums
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.