Jump to content

docker containers don´t start after cache run out of space


Bob@unraid

Recommended Posts

Hello everyone,

yesterday my cache drive ran full / out of space and after that my docker containers aren´t working anymore. All the docker files are located on the cache drive (vDisk: /mnt/user/system/docker/docker.img, appdata: /mnt/user/appdata/)
When I try to start a container I am getting "Execution error Error code 403" or "Execution error Server error".

The live log for the contianer shows e":"open /var/lib/docker/containers/xyz: read-only file system"

 

I ran Balance Status (Perform full balance) and Scrub Status (with Repair corrupted blocks) on the cache drives but it didn´t change anything.

Also read on the forum to delete the docker.img, is this the way to go? Or can I try something else?

 

Thanks

Edited by Bob@unraid
Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...