vaneson

Good Afternoon, Recently, due to some errors on a drive (disk5), I decided to move my docker.img off of that device and on to another drive (disk8). For good measure, I followed the ***OFFICIAL GUIDE*** Restoring your Docker Applications in a New Image File and deleted my docker.img all together off of disk5. Now, it appears I am able to create the docker.img on the new drive, but I am not able to actually start dockerd process. I get the following: Oct 29 09:40:39 Tower root: starting dockerd ... Oct 29 09:40:58 Tower emhttpd: shcmd (240): umount /var/lib/docker I also tried the process on another drve (disk9) and experience the same issue; dockerd tries to start and then unmounts. I have stopped/started and reboot to no avail. Enable Docker is set to YES in settings, but just sits at "STOPPED". Here is the log of my attempts at creating and subsequent dockerd failure to start: disk8: Oct 29 09:38:10 Tower root: Creating new image file: /mnt/disk8/docker.img size: 50G Oct 29 09:38:10 Tower root: btrfs-progs v5.1.1 Oct 29 09:38:10 Tower root: See http://btrfs.wiki.kernel.org for more information. Oct 29 09:38:10 Tower root: Oct 29 09:38:10 Tower root: Label: (null) Oct 29 09:38:10 Tower root: UUID: 884b2bf2-119a-4b06-8d95-2f8d1d6d8a70 Oct 29 09:38:10 Tower root: Node size: 16384 Oct 29 09:38:10 Tower root: Sector size: 4096 Oct 29 09:38:10 Tower root: Filesystem size: 50.00GiB Oct 29 09:38:10 Tower root: Block group profiles: Oct 29 09:38:10 Tower root: Data: single 8.00MiB Oct 29 09:38:10 Tower root: Metadata: DUP 256.00MiB Oct 29 09:38:10 Tower root: System: DUP 8.00MiB Oct 29 09:38:10 Tower root: SSD detected: no Oct 29 09:38:10 Tower root: Incompat features: extref, skinny-metadata Oct 29 09:38:10 Tower root: Number of devices: 1 Oct 29 09:38:10 Tower root: Devices: Oct 29 09:38:10 Tower root: ID SIZE PATH Oct 29 09:38:10 Tower root: 1 50.00GiB /mnt/disk8/docker.img Oct 29 09:38:10 Tower root: Oct 29 09:38:10 Tower kernel: BTRFS: device fsid 884b2bf2-119a-4b06-8d95-2f8d1d6d8a70 devid 1 transid 5 /dev/loop2 Oct 29 09:38:10 Tower kernel: BTRFS info (device loop2): disk space caching is enabled Oct 29 09:38:10 Tower kernel: BTRFS info (device loop2): has skinny extents Oct 29 09:38:10 Tower kernel: BTRFS info (device loop2): flagging fs with big metadata feature Oct 29 09:38:10 Tower kernel: BTRFS info (device loop2): checking UUID tree Oct 29 09:38:10 Tower emhttpd: shcmd (194): /etc/rc.d/rc.docker start Oct 29 09:38:10 Tower root: starting dockerd ... Oct 29 09:38:27 Tower emhttpd: shcmd (196): umount /var/lib/docker disk9: Oct 29 09:40:38 Tower emhttpd: shcmd (236): /usr/local/sbin/mount_image '/mnt/disk9/docker.img' /var/lib/docker 50 Oct 29 09:40:38 Tower root: Creating new image file: /mnt/disk9/docker.img size: 50G Oct 29 09:40:39 Tower root: btrfs-progs v5.1.1 Oct 29 09:40:39 Tower root: See http://btrfs.wiki.kernel.org for more information. Oct 29 09:40:39 Tower root: Oct 29 09:40:39 Tower root: Label: (null) Oct 29 09:40:39 Tower root: UUID: 2127d86d-a398-454b-8c1f-fb5d1aebe8bd Oct 29 09:40:39 Tower root: Node size: 16384 Oct 29 09:40:39 Tower root: Sector size: 4096 Oct 29 09:40:39 Tower root: Filesystem size: 50.00GiB Oct 29 09:40:39 Tower root: Block group profiles: Oct 29 09:40:39 Tower root: Data: single 8.00MiB Oct 29 09:40:39 Tower root: Metadata: DUP 256.00MiB Oct 29 09:40:39 Tower root: System: DUP 8.00MiB Oct 29 09:40:39 Tower root: SSD detected: no Oct 29 09:40:39 Tower root: Incompat features: extref, skinny-metadata Oct 29 09:40:39 Tower root: Number of devices: 1 Oct 29 09:40:39 Tower root: Devices: Oct 29 09:40:39 Tower root: ID SIZE PATH Oct 29 09:40:39 Tower root: 1 50.00GiB /mnt/disk9/docker.img Oct 29 09:40:39 Tower root: Oct 29 09:40:39 Tower kernel: BTRFS: device fsid 2127d86d-a398-454b-8c1f-fb5d1aebe8bd devid 1 transid 5 /dev/loop2 Oct 29 09:40:39 Tower kernel: BTRFS info (device loop2): disk space caching is enabled Oct 29 09:40:39 Tower kernel: BTRFS info (device loop2): has skinny extents Oct 29 09:40:39 Tower kernel: BTRFS info (device loop2): flagging fs with big metadata feature Oct 29 09:40:39 Tower kernel: BTRFS info (device loop2): checking UUID tree Oct 29 09:40:39 Tower emhttpd: shcmd (238): /etc/rc.d/rc.docker start Oct 29 09:40:39 Tower root: starting dockerd ... Oct 29 09:40:58 Tower emhttpd: shcmd (240): umount /var/lib/docker Any help in getting docker.img to start on a new drive would be hlepful. I also recognize that it would be better to put docker.img on a cache/SSD, but that is further down the line. Also, disk5 where docker.img lived originally, is being replaced w/ RMA drive. Thanks, tower-diagnostics-20191029-1308.zip

Just wanted to bump this to the top and thank SlrG. I was tearing my hair out attempting to resolve my docker issue. This fix worked. I have now set my individual docker apps and Open VPN to not auto-start.

I was having an issue with my cache drive being read only. Today I rebooted the array, and now my cache drive (btrfs) is unmountable. I do not want to format, if possible, for obvious reasons. Attached is my Diag dumb, any help would be greatly appreciated. tower-diagnostics-20160902-1541.zip

I am having the same issue. Appears to be configured properly, but also get blank screen on when I VNC in.

The container volume path you added (Movies) is not an absolute path, but is rather a relative path -> the docker system in 6.2+ would have returned that error, unfortunately the docker version included in 6.1.x doesn't state that error. The fix is to set the container path from Movies to be /Movies Thank you very much, thats the fix! Cheers, enjoy a beer!

Just move to unRAID this weekend and am having an issue w/ Plex Media Server showing as an orphan image every time I try to add a "media folder "Container volume/Host path. Initially, if I just create the docker container with the standard /config path and no media path it works, but as soon as I add a "media folder" the docker image becomes an orphan. This happens with the LimeTech, needo and linuxserver.io images. Based on other posts i have ensured my Dynamix webGui app is "up-to-date" (2016.07.27). I have also stopped and restarted the docker plugin several times, ran "Fix Common Problems" plugin, etc. Any help with this would be greatly appreciated! Thanks!