BRiT Posted June 9, 2015 Share Posted June 9, 2015 I'm not sure if this is anything or not, just throwing out some observations as I was reviewing my syslog, I saw the following entries, which had me wondering if maybe there isn't some sort of race conditions or order of operations between: 'docker', 'dnsmasq' '/etc/resolv.conf' file population It looks like Docker starts before /etc/resolv.conf is populated. A possible reason why my dockers work is I setup a read-only map of '/etc/resolv.conf' so when it gets modified on the unRAID host the updates automagically happens in the docker. Jun 8 19:36:53 REAVER emhttp: Starting Docker... Jun 8 19:36:53 REAVER kernel: BTRFS: device fsid a1c17cc3-52cd-4c55-ac64-61cc1943f4d3 devid 1 transid 250202 /dev/loop0 Jun 8 19:36:53 REAVER kernel: BTRFS info (device loop0): disk space caching is enabled Jun 8 19:36:53 REAVER kernel: BTRFS: has skinny extents Jun 8 19:36:53 REAVER logger: Resize '/var/lib/docker' of 'max' Jun 8 19:36:53 REAVER logger: starting docker ... Jun 8 19:36:55 REAVER dnsmasq[8559]: started, version 2.57 cachesize 150 Jun 8 19:36:55 REAVER dnsmasq[8559]: compile time options: IPv6 GNU-getopt no-DBus I18N DHCP TFTP IDN Jun 8 19:36:55 REAVER dnsmasq-dhcp[8559]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h Jun 8 19:36:55 REAVER dnsmasq[8559]: no servers found in /etc/resolv.conf, will retry Then later on in the log I noticed the following: Jun 8 19:36:59 REAVER kernel: br0: port 1(eth0) entered learning state Jun 8 19:37:09 REAVER kernel: docker0: port 1(veth96224dc) entered forwarding state Jun 8 19:37:09 REAVER kernel: docker0: port 2(veth550a1fb) entered forwarding state Jun 8 19:37:10 REAVER kernel: docker0: port 3(veth5fc5e2e) entered forwarding state Jun 8 19:37:14 REAVER kernel: br0: topology change detected, propagating Jun 8 19:37:14 REAVER kernel: br0: port 1(eth0) entered forwarding state And then a bit later I see the following happen... Jun 8 19:39:15 REAVER dnsmasq[8559]: reading /etc/resolv.conf Jun 8 19:39:15 REAVER dnsmasq[8559]: using nameserver 10.0.0.128#53 Link to comment
sparklyballs Posted June 9, 2015 Share Posted June 9, 2015 Also (again): are there any containers which seem more 'susceptible' than others? If so, which ones? sickbeard pretty much fails most times and is the most regular to fail. Link to comment
limetech Posted June 9, 2015 Author Share Posted June 9, 2015 I'm not sure if this is anything or not, just throwing out some observations as I was reviewing my syslog, I saw the following entries, which had me wondering if maybe there isn't some sort of race conditions or order of operations between: 'docker', 'dnsmasq' '/etc/resolv.conf' file population It looks like Docker starts before /etc/resolv.conf is populated. A possible reason why my dockers work is I setup a read-only map of '/etc/resolv.conf' so when it gets modified on the unRAID host the updates automagically happens in the docker. You might be onto something... According to this doc: https://docs.docker.com/articles/networking/ Docker already does exactly what you describe, although it looks to me it's mounted rw. Can you post output of: docker exec <container> mounts of one of your containers? ps. I'd also be grateful if you changed your sig Link to comment
Edrikk Posted June 9, 2015 Share Posted June 9, 2015 regarding lightbox issue on iOS, No I had only reported on the beta and RC threads. I have just created this ticket: https://github.com/bergware/dynamix/issues/3 Link to comment
JaY_III Posted June 9, 2015 Share Posted June 9, 2015 Also (again): are there any containers which seem more 'susceptible' than others? If so, which ones? sickbeard pretty much fails most times and is the most regular to fail. add sonar, sabnzbd to that list. force update "fixes" them Link to comment
BRiT Posted June 9, 2015 Share Posted June 9, 2015 You might be onto something... According to this doc: https://docs.docker.com/articles/networking/ Docker already does exactly what you describe, although it looks to me it's mounted rw. Can you post output of: docker exec <container> mounts of one of your containers? You're correct. It's already mapping RW the /etc/resolv.conf file. I see it listed twice, once RW and once RO. I'm not sure if you recall this or not, but the only reason I even tried mapping it as RO explicitly was the docker was initially using Google 8.8.8.8 as the DNS resolver, despite my settings for unRAID to use my router [10.0.0.128]. I think I posted about it on the forums as a defect report, but not absolutely certain. I think jonp helped out or guided me on how to pass additional options to docker (via repository augmentation), when I was trying to pass DNS options. I wonder if the Docker behavior on /etc/resolv.conf changed between when I noticed the issue and now. EDIT: Found the original defect report, detailed on 2014-11-30 @ http://lime-technology.com/forum/index.php?topic=36533.0 # docker exec EggDrop mount /dev/loop0 on / type btrfs (rw,relatime,space_cache) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev type tmpfs (rw,nosuid,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666) shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k) mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime) sysfs on /sys type sysfs (ro,nosuid,nodev,noexec,relatime) /dev/sdc1 on /config type xfs (rw,noatime,nodiratime,attr2,inode64,noquota) rootfs on /etc/localtime type rootfs (ro,size=4042636k,nr_inodes=1010659) rootfs on /etc/resolv.conf type rootfs (ro,size=4042636k,nr_inodes=1010659) /dev/sdc1 on /logs type xfs (rw,noatime,nodiratime,attr2,inode64,noquota) rootfs on /tmp type rootfs (rw,size=4042636k,nr_inodes=1010659) /dev/loop0 on /etc/resolv.conf type btrfs (rw,relatime,space_cache) /dev/loop0 on /etc/hostname type btrfs (rw,relatime,space_cache) /dev/loop0 on /etc/hosts type btrfs (rw,relatime,space_cache) proc on /proc/bus type proc (ro,nosuid,nodev,noexec,relatime) proc on /proc/fs type proc (ro,nosuid,nodev,noexec,relatime) proc on /proc/irq type proc (ro,nosuid,nodev,noexec,relatime) proc on /proc/sys type proc (ro,nosuid,nodev,noexec,relatime) proc on /proc/sysrq-trigger type proc (ro,nosuid,nodev,noexec,relatime) tmpfs on /proc/kcore type tmpfs (rw,nosuid,mode=755) Link to comment
limetech Posted June 9, 2015 Author Share Posted June 9, 2015 You guys who see this, please refer to: http://lime-technology.com/forum/index.php?topic=40503.msg381738#msg381738 And post your results please. Link to comment
limetech Posted June 9, 2015 Author Share Posted June 9, 2015 I wonder if the Docker behavior on /etc/resolv.conf changed between when I noticed the issue and now. Thanks for the info. Yes there have been changes in how docker deals with dns. If you google 'docker containers lose dns' it's not a rare problem, but most of those hits are pretty old. Edit: docker's mount over /etc/resolve.conf is overruling yours Link to comment
AndreM Posted June 9, 2015 Share Posted June 9, 2015 I'm wiith sparky running pfsense as well and also getting random dns issues maybe thats a coiencdence or not .. ill check for the different things you mentioned above and report back I'm also using pfSense (on dedicated, bare-metal) as my default gateway and DNS server, and my dockers are all working. I'm even using a few of Sparkly's dockers, and I've not run into DNS issues with any of them. They are all set to auto-start and my server restarts at least twice a week due to constant power cuts in my country. Link to comment
mr-hexen Posted June 9, 2015 Share Posted June 9, 2015 My issue with dns occurred a few days after setting up win7 and Ubuntu server vms. Couch potato by needo was the one that I noticed first. Link to comment
limetech Posted June 9, 2015 Author Share Posted June 9, 2015 Ok is there anyone who has seen this docker dns issue who is also NOT running any VM's?? Link to comment
BRiT Posted June 9, 2015 Share Posted June 9, 2015 I wonder if the Docker behavior on /etc/resolv.conf changed between when I noticed the issue and now. Thanks for the info. Yes there have been changes in how docker deals with dns. If you google 'docker containers lose dns' it's not a rare problem, but most of those hits are pretty old. Edit: docker's mount over /etc/resolve.conf is overruling yours Oddly enough, the two /etc/resolv.conf are not identical; host does not match docker containers. So Docker itself must be doing some processing of the file. I'd expect to see the exact same comments in the container. EDIT: I am NOT seeing the issue and I am NOT running any VMs (yet). root@REAVER:~# docker exec EggDrop cat /etc/resolv.conf nameserver 10.0.0.128 # docker exec EggDrop cat /etc/hosts 172.17.0.1 7710df941f84 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters root@REAVER:~# docker exec EggDrop cat /etc/hostname 7710df941f84 root@REAVER:~# cat /etc/resolv.conf # Generated by dhcpcd from br0 # /etc/resolv.conf.head can replace this line nameserver 10.0.0.128 # /etc/resolv.conf.tail can replace this line root@REAVER:~# cat /etc/hosts # Generated 127.0.0.1 REAVER localhost root@REAVER:~# hostname REAVER Link to comment
limetech Posted June 9, 2015 Author Share Posted June 9, 2015 I wonder if the Docker behavior on /etc/resolv.conf changed between when I noticed the issue and now. Thanks for the info. Yes there have been changes in how docker deals with dns. If you google 'docker containers lose dns' it's not a rare problem, but most of those hits are pretty old. Edit: docker's mount over /etc/resolve.conf is overruling yours Oddly enough, the two /etc/resolv.conf are not identical; host does not match docker containers. So Docker itself must be doing some processing of the file. I'd expect to see the exact same comments in the container. EDIT: I am NOT seeing the issue and I am NOT running any VMs (yet). root@REAVER:~# docker exec EggDrop cat /etc/resolv.conf nameserver 10.0.0.128 # docker exec EggDrop cat /etc/hosts 172.17.0.1 7710df941f84 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters root@REAVER:~# docker exec EggDrop cat /etc/hostname 7710df941f84 root@REAVER:~# cat /etc/resolv.conf # Generated by dhcpcd from br0 # /etc/resolv.conf.head can replace this line nameserver 10.0.0.128 # /etc/resolv.conf.tail can replace this line root@REAVER:~# cat /etc/hosts # Generated 127.0.0.1 REAVER localhost root@REAVER:~# hostname REAVER Are you doing anything "custom" to enable ipv6? Link to comment
sparklyballs Posted June 9, 2015 Share Posted June 9, 2015 I wonder if the Docker behavior on /etc/resolv.conf changed between when I noticed the issue and now. Thanks for the info. Yes there have been changes in how docker deals with dns. If you google 'docker containers lose dns' it's not a rare problem, but most of those hits are pretty old. Edit: docker's mount over /etc/resolve.conf is overruling yours Oddly enough, the two /etc/resolv.conf are not identical; host does not match docker containers. So Docker itself must be doing some processing of the file. I'd expect to see the exact same comments in the container. EDIT: I am NOT seeing the issue and I am NOT running any VMs (yet). root@REAVER:~# docker exec EggDrop cat /etc/resolv.conf nameserver 10.0.0.128 # docker exec EggDrop cat /etc/hosts 172.17.0.1 7710df941f84 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters root@REAVER:~# docker exec EggDrop cat /etc/hostname 7710df941f84 root@REAVER:~# cat /etc/resolv.conf # Generated by dhcpcd from br0 # /etc/resolv.conf.head can replace this line nameserver 10.0.0.128 # /etc/resolv.conf.tail can replace this line root@REAVER:~# cat /etc/hosts # Generated 127.0.0.1 REAVER localhost root@REAVER:~# hostname REAVER Are you doing anything "custom" to enable ipv6? i was just about to ask that, i have a container on hold because it needs ipv6. Link to comment
BRiT Posted June 9, 2015 Share Posted June 9, 2015 I wonder if the Docker behavior on /etc/resolv.conf changed between when I noticed the issue and now. Thanks for the info. Yes there have been changes in how docker deals with dns. If you google 'docker containers lose dns' it's not a rare problem, but most of those hits are pretty old. Edit: docker's mount over /etc/resolve.conf is overruling yours Oddly enough, the two /etc/resolv.conf are not identical; host does not match docker containers. So Docker itself must be doing some processing of the file. I'd expect to see the exact same comments in the container. EDIT: I am NOT seeing the issue and I am NOT running any VMs (yet). root@REAVER:~# docker exec EggDrop cat /etc/resolv.conf nameserver 10.0.0.128 # docker exec EggDrop cat /etc/hosts 172.17.0.1 7710df941f84 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters root@REAVER:~# docker exec EggDrop cat /etc/hostname 7710df941f84 root@REAVER:~# cat /etc/resolv.conf # Generated by dhcpcd from br0 # /etc/resolv.conf.head can replace this line nameserver 10.0.0.128 # /etc/resolv.conf.tail can replace this line root@REAVER:~# cat /etc/hosts # Generated 127.0.0.1 REAVER localhost root@REAVER:~# hostname REAVER Are you doing anything "custom" to enable ipv6? I don't even have IPV6 deployed or enabled on my router or any of my servers. I am perhaps more baffled than you to see it even show up. I wonder if it captured that at the time of "docker build". The docker container is using phusion 0.9.16 as a base and was created using Boot2Docker on a Windows 7 OS. It looks like the Boot2Docker has IPV6 setup via VirtualBox so maybe that played a part? PS C:\Windows\system32> ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : Serenity Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Ethernet: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) 82578DM Gigabit Network Connection Physical Address. . . . . . . . . : 00-01-2E-2F-14-56 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::6d03:76a3:ea8b:8691%3(Preferred) IPv4 Address. . . . . . . . . . . : 10.0.0.19(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Tuesday, May 26, 2015 5:34:40 PM Lease Expires . . . . . . . . . . : Friday, July 16, 2151 3:49:44 AM Default Gateway . . . . . . . . . : 10.0.0.128 DHCP Server . . . . . . . . . . . : 10.0.0.128 DHCPv6 IAID . . . . . . . . . . . : 50331950 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-B2-E7-FA-00-01-2E-2F-14-56 DNS Servers . . . . . . . . . . . : 10.0.0.128 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter VirtualBox Host-Only Network: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter Physical Address. . . . . . . . . : 08-00-27-00-E4-63 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::74a7:d1d1:624c:961c%9(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : DHCPv6 IAID . . . . . . . . . . . : 134742055 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-B2-E7-FA-00-01-2E-2F-14-56 DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter VirtualBox Host-Only Network #2: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter #2 Physical Address. . . . . . . . . : 08-00-27-00-70-FD DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::b051:1a94:43e7:d00b%12(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.59.3(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : DHCPv6 IAID . . . . . . . . . . . : 319291431 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-B2-E7-FA-00-01-2E-2F-14-56 DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled I attached the Docker build file used, so you can see there's nothing "custom" in there other than addin in the run time script and install scripts along with the ports and mappings. I also attached screenshots of the unRAID Network Settings and Docker Settings to show nothing custom there either. Here's more info from the docker container, which only shows 2 devices using ipv4 root@REAVER:~# docker exec EggDrop ifconfig eth0 Link encap:Ethernet HWaddr 02:42:ac:11:00:01 inet addr:172.17.0.1 Bcast:0.0.0.0 Mask:255.255.0.0 UP BROADCAST RUNNING MTU:1500 Metric:1 RX packets:305 errors:0 dropped:0 overruns:0 frame:0 TX packets:217 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:48737 (48.7 KB) TX bytes:20590 (20.5 KB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Dockerfile.txt Link to comment
htpcnewbie Posted June 9, 2015 Share Posted June 9, 2015 This may be unrelated to rc5 but I remember seeing this in one of beta releases. A plugin update (community repositories) failed due to no space in /var/log. How do I fix this? Filesystem Size Used Avail Use% Mounted on tmpfs 128M 128M 0 100% /var/log /dev/sda1 30G 6.8G 23G 24% /boot /dev/md1 2.8T 1.9T 903G 68% /mnt/disk1 ... .. /dev/sdp1 676G 488G 185G 73% /mnt/cache shfs 32T 21T 12T 64% /mnt/user0 shfs 33T 21T 12T 64% /mnt/user /dev/loop0 20G 5.0G 14G 27% /var/lib/docker /dev/loop1 1.4M 116K 1.2M 9% /etc/libvirt Link to comment
ysss Posted June 9, 2015 Share Posted June 9, 2015 Upgraded from rc2... now my Docker tab is gone. Hmm. Link to comment
htpcnewbie Posted June 9, 2015 Share Posted June 9, 2015 Go to settings and click on enable docker. Upgraded from rc2... now my Docker tab is gone. Hmm. Link to comment
montery Posted June 9, 2015 Share Posted June 9, 2015 Wasn't expecting a new RC so fast! Just wanted to report that System Status is reporting the maximum amount of memory my motherboard can store, rather than the actual amount installed. Allocated is indicating the actual amount installed. System Information reports things correctly. Very minor, but, hey, I like to contribute where I can! Link to comment
mikefallen Posted June 9, 2015 Share Posted June 9, 2015 Ok is there anyone who has seen this docker dns issue who is also NOT running any VM's?? me i'm not running any vms only bare metal unraid (with dockers of course) and my pfsense is running in vmware esx5 server that is completely separate although i don't think this really has anything to do with it but worth mentioning. But i didn''t have any DNS issues on my dockers since the upgrade to rc5 Link to comment
ysss Posted June 9, 2015 Share Posted June 9, 2015 Go to settings and click on enable docker. Upgraded from rc2... now my Docker tab is gone. Hmm. It was already enabled. Is there a listing of all pertinent docker related files in unraid? I'd like to make manual backup of them before I mess around. I only know of the docker.img, /boot/config/docker.cfg and the individual docker's appdatas... what about the listing of all the docker settings? (port and directory mapping, etc). Link to comment
htpcnewbie Posted June 9, 2015 Share Posted June 9, 2015 The user templates are stored in the config directory. I added the community repositories plugin and used the templates from there to create all the dockers fresh in rc3. I also remember that going from rc2 to rc3, the dockers had to be redone. I think it may be better if someone knowledgeable confirms this before you start on the effort. Go to settings and click on enable docker. Upgraded from rc2... now my Docker tab is gone. Hmm. It was already enabled. Is there a listing of all pertinent docker related files in unraid? I'd like to make manual backup of them before I mess around. I only know of the docker.img, /boot/config/docker.cfg and the individual docker's appdatas... what about the listing of all the docker settings? (port and directory mapping, etc). Link to comment
ysss Posted June 9, 2015 Share Posted June 9, 2015 The user templates are stored in the config directory. I added the community repositories plugin and used the templates from there to create all the dockers fresh in rc3. I also remember that going from rc2 to rc3, the dockers had to be redone. I think it may be better if someone knowledgeable confirms this before you start on the effort. Go to settings and click on enable docker. Upgraded from rc2... now my Docker tab is gone. Hmm. It was already enabled. Is there a listing of all pertinent docker related files in unraid? I'd like to make manual backup of them before I mess around. I only know of the docker.img, /boot/config/docker.cfg and the individual docker's appdatas... what about the listing of all the docker settings? (port and directory mapping, etc). If it's in /boot/config, it seems that mine are gone... root@archive:/boot/config# ls -al /boot/config total 92 drwxrwxrwx 5 root root 4096 Jun 9 09:39 ./ drwxrwxrwx 13 root root 4096 Jan 1 1970 ../ -rwxrwxrwx 1 root root 256 Apr 27 03:56 Pro.key* -rwxrwxrwx 1 root root 256 Jul 8 2013 Pro.oldkey* -rwxrwxrwx 1 root root 9336 Jun 9 09:09 disk.cfg* -rwxrwxrwx 1 root root 130 Jun 9 09:33 docker.cfg* -rwxrwxrwx 1 root root 80 Jun 9 09:37 domain.cfg* -rwxrwxrwx 1 root root 138 Mar 6 23:41 flash.cfg* -rwxrwxrwx 1 root root 71 Apr 17 22:38 go* -rwxrwxrwx 1 root root 566 May 28 01:43 group* -rwxrwxrwx 1 root root 356 May 5 02:21 ident.cfg* -rwxrwxrwx 1 root root 259 May 15 11:02 network.cfg* -rwxrwxrwx 1 root root 1249 May 31 11:25 passwd* drwxrwxrwx 9 root root 4096 Jun 9 08:48 plugins/ -rwxrwxrwx 1 root root 698 May 31 11:25 shadow* -rwxrwxrwx 1 root root 502 May 5 02:21 share.cfg* drwxrwxrwx 2 root root 4096 Jun 9 09:12 shares/ -rwxrwxrwx 1 root root 1041 May 31 11:25 smbpasswd* drwxrwxrwx 2 root root 4096 Apr 27 03:47 ssh/ -rwxrwxrwx 1 root root 4096 Jun 9 09:09 super.dat* -rwxrwxrwx 1 root root 4096 May 1 12:38 super.old* root@archive:/boot/config# cat docker.cfg DOCKER_OPTS="--storage-driver=btrfs" DOCKER_IMAGE_FILE="/mnt/cache/docker/docker.img" DOCKER_IMAGE_SIZE="15" DOCKER_ENABLED="yes" Btw, yes docker share is set to cache-only... and I don't use any openvpn client on this unraid box. Link to comment
Squid Posted June 9, 2015 Share Posted June 9, 2015 This may be unrelated to rc5 but I remember seeing this in one of beta releases. A plugin update (community repositories) failed due to no space in /var/log. How do I fix this? Filesystem Size Used Avail Use% Mounted on tmpfs 128M 128M 0 100% /var/log /dev/sda1 30G 6.8G 23G 24% /boot /dev/md1 2.8T 1.9T 903G 68% /mnt/disk1 ... .. /dev/sdp1 676G 488G 185G 73% /mnt/cache shfs 32T 21T 12T 64% /mnt/user0 shfs 33T 21T 12T 64% /mnt/user /dev/loop0 20G 5.0G 14G 27% /var/lib/docker /dev/loop1 1.4M 116K 1.2M 9% /etc/libvirt http://lime-technology.com/forum/index.php?topic=31752.msg374338#msg374338 Link to comment
Squid Posted June 9, 2015 Share Posted June 9, 2015 The user templates are stored in the config directory. I added the community repositories plugin and used the templates from there to create all the dockers fresh in rc3. I also remember that going from rc2 to rc3, the dockers had to be redone. I think it may be better if someone knowledgeable confirms this before you start on the effort. Go to settings and click on enable docker. Upgraded from rc2... now my Docker tab is gone. Hmm. It was already enabled. Is there a listing of all pertinent docker related files in unraid? I'd like to make manual backup of them before I mess around. I only know of the docker.img, /boot/config/docker.cfg and the individual docker's appdatas... what about the listing of all the docker settings? (port and directory mapping, etc). If it's in /boot/config, it seems that mine are gone... root@archive:/boot/config# ls -al /boot/config total 92 drwxrwxrwx 5 root root 4096 Jun 9 09:39 ./ drwxrwxrwx 13 root root 4096 Jan 1 1970 ../ -rwxrwxrwx 1 root root 256 Apr 27 03:56 Pro.key* -rwxrwxrwx 1 root root 256 Jul 8 2013 Pro.oldkey* -rwxrwxrwx 1 root root 9336 Jun 9 09:09 disk.cfg* -rwxrwxrwx 1 root root 130 Jun 9 09:33 docker.cfg* -rwxrwxrwx 1 root root 80 Jun 9 09:37 domain.cfg* -rwxrwxrwx 1 root root 138 Mar 6 23:41 flash.cfg* -rwxrwxrwx 1 root root 71 Apr 17 22:38 go* -rwxrwxrwx 1 root root 566 May 28 01:43 group* -rwxrwxrwx 1 root root 356 May 5 02:21 ident.cfg* -rwxrwxrwx 1 root root 259 May 15 11:02 network.cfg* -rwxrwxrwx 1 root root 1249 May 31 11:25 passwd* drwxrwxrwx 9 root root 4096 Jun 9 08:48 plugins/ -rwxrwxrwx 1 root root 698 May 31 11:25 shadow* -rwxrwxrwx 1 root root 502 May 5 02:21 share.cfg* drwxrwxrwx 2 root root 4096 Jun 9 09:12 shares/ -rwxrwxrwx 1 root root 1041 May 31 11:25 smbpasswd* drwxrwxrwx 2 root root 4096 Apr 27 03:47 ssh/ -rwxrwxrwx 1 root root 4096 Jun 9 09:09 super.dat* -rwxrwxrwx 1 root root 4096 May 1 12:38 super.old* root@archive:/boot/config# cat docker.cfg DOCKER_OPTS="--storage-driver=btrfs" DOCKER_IMAGE_FILE="/mnt/cache/docker/docker.img" DOCKER_IMAGE_SIZE="15" DOCKER_ENABLED="yes" Btw, yes docker share is set to cache-only... and I don't use any openvpn client on this unraid box. All of the port mappings, etc are store in /boot/config/plugins/dockerMan/templates-user Link to comment
Recommended Posts