November 21, 201510 yr Hi all, Just noticed after recent restart of server that there was no Docker tab and that I couldn't load any of the services from it. No errors in the syslog on the Web GUI. I just did a docker -d on the command line and I got this message: INFO[0000] Listening for HTTP on unix (/var/run/docker.sock) INFO[0000] [graphdriver] using prior storage driver "btrfs" FATA[0000] Error starting daemon: Insertion failed because database is full: database or disk is full Disk space isn't full, I've also since made the Docker image 20gb instead of 10gb but the same error occurs. Could anyone lend me a hand?
January 23, 201610 yr Hi, I got the same error you did. INFO[0000] [graphdriver] using prior storage driver "btrfs" INFO[0000] Listening for HTTP on unix (/var/run/docker.sock) FATA[0000] Error starting daemon: Insertion failed because database is full: database or disk is full If you run df -h you should se a list of directories and space available. For my case, the docker image was 100% full. /dev/loop0 15G 14G 0 100% /var/lib/docker I was pretty perplexed but after a little googleing there appears to be a bug with docker not properly destroying btrfs subvolumes after a container is destroyed https://github.com/docker/docker/issues/9939. I did a little poking around with this: ls -a /var/lib/docker/btrfs/subvolumes I saw that it was filled with a bunch of stuff so I did this to see exactly how much is in there: du -sbh /var/lib/docker/btrfs/subvolumes The command took too long to run, I wasn't sure what was going on with it. I took off the s option so I could see what the command was doing, there appears to be hundreds of files in there. Docker apparently hasn't fixed it yet but somebody wrote a script to safely clean out that directory https://github.com/docker/docker/blob/620339f166984540f15aadef2348646eee9a5b42/contrib/nuke-graph-directory.sh. I'm going to try running that script now, I'll let you know how it works out.
January 23, 201610 yr That script didn't help. Maybe it serves a different purpose, I didn't feel like re reading that forum. It only appeared to do a rm -Rf on the given directory and then unmounting the docker image. Here's what I did to get my docker working again. I unmounted the docker image and then I deleted the image. Then I uninstalled the docker plugin from the web ui. I then restarted the server. When the server restarted I was able to make new containers using some of the "my" templates in order to get the container configured exactly as it was before. After doing this with my plex I didn't need to rescan my libraries since all of that was saved in my appdata folder. All of my containers are back up and running now and I have plenty of space available on the image. This is probably more of a workaround rather than a solution.
January 23, 201610 yr Here's what I did to get my docker working again. I unmounted the docker image and then I deleted the image. Then I uninstalled the docker plugin from the web ui. If you mean that you uninstalled the dockerMan plugin, then that was probably your whole problem, as that plugin was incorporated (and vastly improved) since probably at least 6.0B10
Archived
This topic is now archived and is closed to further replies.