March 17, 20179 yr Good morning! The other day I noticed my docker's weren't running and I thought I had a bad drive. I removed everything from the cache drive, reformatted, and ran the checkdisk and xfs utilities on it, everything looked good. I put the cache back in and started with a fresh docker image (my appdata is saved elsewhere so I thought I'd just start clean). But now docker won't start, and I'm getting the following over and over again in my log. I've also attached the diagnostic info. Any ideas? Thank you! Mar 17 11:55:01 REBEL-DATA kernel: BTRFS info (device loop2): disk space caching is enabled Mar 17 11:55:01 REBEL-DATA kernel: BTRFS info (device loop2): has skinny extents Mar 17 11:55:01 REBEL-DATA root: Resize '/var/lib/docker' of 'max' Mar 17 11:55:01 REBEL-DATA kernel: BTRFS info (device loop2): new size for /dev/loop2 is 128849018880 Mar 17 11:55:01 REBEL-DATA emhttp: shcmd (973): /etc/rc.d/rc.docker start |& logger Mar 17 11:55:02 REBEL-DATA root: starting docker ... Mar 17 11:55:03 REBEL-DATA emhttp: shcmd (975): umount /var/lib/docker |& logger rebel-data-diagnostics-20170317-1152.zip
March 17, 20179 yr Community Expert Why have you set your docker.img so large? I've never heard of anyone who thought they needed more than 20G except for people who were doing it wrong.
March 17, 20179 yr Author That's an artifact from when I was doing it wrong. I used to have a lot of data stored in the docker image. I can reduce it now, once I get it working that is.
March 17, 20179 yr Author I ended up just blowing the disk away and starting from scratch. I moved the docker.img file to an SSD outside my array that is mounted via the unmounted disk pluggin.
Archived
This topic is now archived and is closed to further replies.