danofun

mr. balls, please try these commands and post output: cat /etc/resolv.conf cat /etc/hosts hostname Then pick one of your containers with no dns and type: docker exec <container-name> cat /etc/resolv.conf docker exec <container-name> cat /etc/hosts docker exec <container-name> cat /etc/hostname replacing <container-name> with the actual container name. give me a little while, i've cycled them bridge to host and host to bridge and they're all active. just working on something on the server. here are the results of above run on a docker currently experiencing the DNS issue. root@GianGi:~# cat /etc/resolv.conf # Generated by dhcpcd from br0 # /etc/resolv.conf.head can replace this line domain fios-router.home nameserver 192.168.1.1 # /etc/resolv.conf.tail can replace this line root@GianGi:~# cat /etc/hosts # Generated 127.0.0.1 GianGi localhost root@GianGi:~# hostname GianGi root@GianGi:~# docker exec NZBGet cat /etc/resolv.conf nameserver 8.8.8.8 nameserver 8.8.4.4root@GianGi:~# docker exec NZBGet cat /etc/hosts 172.17.0.2 dae7d1bb71d5 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@GianGi:~# docker exec NZBGet cat /etc/hostname dae7d1bb71d5

thanks for the info bmfrosty, as you might be able to tell this is one of the few docker images i have created which i dont actually use :-). ive now included both unzip and unrar to the image, plsu 14.2 has just been released on the official arch repo, so this is also now included, go grab it :-). @binhex Phenomenal work keeping these docker apps up to date. Your contributions to the community are greatly appreciated! I recently installed your nzbget docker app and it is working quite well with the exception of a few popular addon scripts. It seems all of the nzbget scripts are python2 compatible but many are not compatible with python3. I've executed "ln -sf /usr/bin/python2 /usr/bin/python" within the docker app so python2 is used by default. This has corrected all of the nzbget plugin errors I was receiving. I'm sure others have experienced issues with addons so this might be worth a global add. root@unRAID:~# docker exec -it binhex-nzbget /bin/bash [root@1c6358a5a5ca /]# ls -l /usr/bin/python lrwxrwxrwx 1 root root 7 Feb 26 10:25 python -> python3 [root@1c6358a5a5ca /]# ls -l /usr/bin/python2 lrwxrwxrwx 1 root root 9 Dec 10 23:51 python2 -> python2.7 [root@1c6358a5a5ca /]# ln -sf /usr/bin/python2 /usr/bin/python [root@1c6358a5a5ca /]# ls -l /usr/bin/python lrwxrwxrwx 1 root root 7 May 7 11:50 python -> python2

I can confirm that my single-partition, btrfs-formatted cache drive displaying as "unformatted" after the b13 upgrade was created using cgdisk from the b12 command line, not the GUI.

As mentioned by others, my cache drive now displays as unformatted. Unlike the previous posts, mine was btrfs formatted. Manually mounting the device results in a "bad superblock" message. I'm a long time unRAID user and am happy to financially contribute. That being said, I have a hard time justifying an upgrade from a free/trial license when my entire cache drive has just been compromised by a system upgrade. To be fair, it is a beta. Completely agree and the "use at your own risk" is blazoned across the first post. Simply bad timing for a major issue reported by multiple users.

As mentioned by others, my cache drive now displays as unformatted. Unlike the previous posts, mine was btrfs formatted. Manually mounting the device results in a "bad superblock" message. I'm a long time unRAID user and am happy to financially contribute. That being said, I have a hard time justifying an upgrade from a free/trial license when my entire cache drive has just been compromised by a system upgrade.

@hurrircanehernadez Great work! Any luck porting this to a trusty docker? Is it possible to add beets to your template repo?

I can confirm that this product does work in Windows 8.