RichG

Thanks - that makes much more sense now. I should have realised. And thanks for the great tool. Will make dockers much more useful - I can ditch a couple of VMs now. Cheers.

Well - just had a forehead slapping moment! I removed the '@'s around the docker name in the extra parameters: -e 'pipework_cmd=br0 transmission 192.168.1.3/[email protected]' And it works. I took the instructions too literally.

Thanks ken-ji - that looks like a good alternative if I can't get pipework working.

Thanks. I was thinking it must be related to the way the bridge was set up but I don't see anything out of place: root@Tower:~# ifconfig br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.2 netmask 255.255.255.0 broadcast 0.0.0.0 ether xxxxxxxxxx txqueuelen 1000 (Ethernet) RX packets 4614 bytes 1160833 (1.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2766 bytes 648307 (633.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0 ether xxxxxxxxxx txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 ether xxxxxxxxxx txqueuelen 1000 (Ethernet) RX packets 4615 bytes 1235407 (1.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2741 bytes 638227 (623.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.255.255.255 loop txqueuelen 1 (Local Loopback) RX packets 404 bytes 38987 (38.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 404 bytes 38987 (38.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@Tower:~#

Hi, I'm struggling to get this working - I've a few different things I want to use this for but have been testing with a Transmission docker. My unRaid is the current version and I'm using pipework-1.1.6. I believe I have set up both pipework and transmission dockers correctly. Pipework is set to 'host' and Transmission to 'none' and extra parameters -e 'pipework_cmd=br0 @transmission@ 192.168.1.3/[email protected]' Checking the transmission docker shows no network connection (only loopback): root@Tower:~# docker exec -it transmission ifconfig 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:1 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Pipework log shows: event_line=2017-03-08T15:28:33.713249319Z container start 804a43d744b33c72c6aaf968d8c3552646278eec8b209d41587ec3e2a9ce3305 (build_version=Linuxserver.io version:- 54 Build-date:- March-04-2017-12:22:56-UTC, image=linuxserver/transmission, name=transmission) Device "eth1" does not exist. Looks like no ethernet interface is being substantiated in the docker. Any help here would be much appreciated. Thanks.

Thanks again. I've read that post, and also a couple of threads regarding the phone home feature in the beta/rc versions, and I'm pretty confident now that I don't need to be concerned about this. That's a big relief as I thought I was going to be looking elsewhere for a while. On with the trial ....

Thanks for the responses. Good to know the full release doesn't work like this. However i'd like confirmation from LimeTech that this is, and will continue to be, the case before I buy into the product. Cheers.

Hi guys, New user here. Been running Unraid on trial license for a few days and liking what I see. Until this morning, that is, when my router (pfSense) had a hardware issue and went down. Had to power down my rack to get the router out I and when I go to start back up Unraid it complains it can't connect to the license server. Ooops. So is this just an issue with the trial keys or the same for full license? Is there any mitigation to allow licensed Unraid to run without working internet connection? If I'm forced to have a working internet to be able to use Unraid, then I'm afraid that's a BIG NO NO for me and I'll have to wave it goodbye. Which will be a massive shame. Cheers.