SkilledAlpaca

Implemented Option 1 from the thread Kyle linked above. I was able to start my docker containers after running it manually without any need to disable and renable the Docker service. At least there is a temporary workaround now.

Rebooting Unraid and everything that was having issues started working again. Updated a container and it worked no issue.

Upgraded to 6.12.1 and I have the same issue as others here. docker run -d --name='freshrss' --net='bridge' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="freshrss" -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='022' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:80]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/freshrss-logo.png' -p '8096:80/tcp' -v '/mnt/user/appdata/freshrss':'/config':'rw' 'lscr.io/linuxserver/freshrss' e1f1a6b17997a665637d3ea6732f5792b650383329722f5fd5881c1cb492f2c3 docker: Error response from daemon: failed to start shim: symlink /var/lib/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/e1f1a6b17997a665637d3ea6732f5792b650383329722f5fd5881c1cb492f2c3 /var/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/e1f1a6b17997a665637d3ea6732f5792b650383329722f5fd5881c1cb492f2c3/work: no space left on device: unknown. The command failed.

Upgraded from 6.11.5 to 6.12. My Nvidia driver plugin was removed and caused a couple docker containers to not start. Reinstalling the plugin, disabling and re-enabling Docker fixed that issue. Otherwise the upgrade was smooth.