unRAID Server Release 6.0-rc3-x86_64 Available


447 posts in this topic Last Reply

Recommended Posts

for me docker dont work, with update to rc1 i start getting error

time="2015-05-17T01:28:46+01:00" level=info msg="+job init_networkdriver()"
time="2015-05-17T01:28:46+01:00" level=info msg="+job serveapi(unix:///var/run/docker.sock)"
time="2015-05-17T01:28:46+01:00" level=info msg="Listening for HTTP on unix (/var/run/docker.sock)"
Could not find a free IP address range for interface 'docker0'. Please configure its address manually and run 'docker -b docker0'
time="2015-05-17T01:28:46+01:00" level=info msg="-job init_networkdriver() = ERR (1)"
time="2015-05-17T01:28:46+01:00" level=fatal msg="Shutting down daemon due to errors: Could not find a free IP address range for interface 'docker0'. Please configure its address manually and run 'docker -b docker0'"

 

after downgrade to beta15 eveything working

 

UPDATE:

i know now where is problem, im using Openvpn client with option to start with array.

When i stoped Openvpn client - then Docker starting without problem

 

Now question why is problem with this on rc1 and on b15 works fine ?

Link to post
  • Replies 446
  • Created
  • Last Reply

Top Posters In This Topic

Anyone having an issue with getting the plex docker to connect to its outside world port? Mine won't connect.

 

Ps digging the new VM page. The icons add a very nice touch. Also the 3rd party agents are another amazing feature!

Link to post

Anyone having an issue with getting the plex docker to connect to its outside world port? Mine won't connect.

 

Ps digging the new VM page. The icons add a very nice touch. Also the 3rd party agents are another amazing feature!

 

not with plex, but with virtually every other container i have, that needs to talk to the internet.

 

http://lime-technology.com/forum/index.php?topic=39948.msg374784#msg374784

Link to post

Anyone having an issue with getting the plex docker to connect to its outside world port? Mine won't connect.

 

Ps digging the new VM page. The icons add a very nice touch. Also the 3rd party agents are another amazing feature!

 

not with plex, but with virtually every other container i have, that needs to talk to the internet.

 

http://lime-technology.com/forum/index.php?topic=39948.msg374784#msg374784

I have zero problems with mine, but I don't run any VM's
Link to post

 

Anyone having an issue with getting the plex docker to connect to its outside world port? Mine won't connect.

 

Ps digging the new VM page. The icons add a very nice touch. Also the 3rd party agents are another amazing feature!

 

not with plex, but with virtually every other container i have, that needs to talk to the internet.

 

http://lime-technology.com/forum/index.php?topic=39948.msg374784#msg374784

 

Confirmed, changed my plex network from host to bridge, then bridge to host and now my port is forwarded.... @LT let me know if you need any further information (syslogs etc) from me.

Link to post
I'll get around to rebuilding my Arch VM in KVM now.

 

If you succeed, I'd be interested in some pointers.  I followed the install guide from the Arch Wiki, inasmuch as it can be applied to a VM.  I booted the iso, did the pacstrap etc, but when I reboot to the new installation I just get a blank screen.

Link to post

Jesus, I haven't even rebooted to update to rc1, do I have to reboot first or can I update to rc2 and reboot?

Dont need to reboot first. Update to rc2 right from rc1.

Link to post

VM's don't survive a reboot.

The img files are present on the disk but the cfg files are gone (edit: if they even existed in rc1) after a reboot.

I'm not sure to what you are referring. I don't see any issues with VM after reboot in rc1 or 2. 

Link to post

I'm on RC2, and i have two bridge, but I only set br0 in the settings for both network and for the VM Manager, but anyway I see virbr0

 

So where come the virbr0 from ?

 

ifconfig
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.190  netmask 255.255.255.0  broadcast 192.168.0.255
        ether bc:5f:f4:75:8a:21  txqueuelen 0  (Ethernet)
        RX packets 1975  bytes 269930 (263.6 KiB)
        RX errors 0  dropped 1  overruns 0  frame 0
        TX packets 3263  bytes 1157572 (1.1 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.42.1  netmask 255.255.0.0  broadcast 0.0.0.0
        ether 00:00:00:00:00:00  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 88  bytes 14377 (14.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
        ether bc:5f:f4:75:8a:21  txqueuelen 1000  (Ethernet)
        RX packets 1996  bytes 306274 (299.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3263  bytes 1161129 (1.1 MiB)
        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.0.0.0
        loop  txqueuelen 0  (Local Loopback)
        RX packets 466  bytes 284389 (277.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 466  bytes 284389 (277.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1500
        inet 10.22.0.1  netmask 255.255.255.0  destination 10.22.0.1
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 100  (UNSPEC)
        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

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 52:54:00:0e:5c:57  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

Link to post

I'm on RC2, and i have two bridge, but I only set br0 in the settings for both network and for the VM Manager, but anyway I see virbr0

 

So where come the virbr0 from ?

 

ifconfig
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.190  netmask 255.255.255.0  broadcast 192.168.0.255
        ether bc:5f:f4:75:8a:21  txqueuelen 0  (Ethernet)
        RX packets 1975  bytes 269930 (263.6 KiB)
        RX errors 0  dropped 1  overruns 0  frame 0
        TX packets 3263  bytes 1157572 (1.1 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.42.1  netmask 255.255.0.0  broadcast 0.0.0.0
        ether 00:00:00:00:00:00  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 88  bytes 14377 (14.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
        ether bc:5f:f4:75:8a:21  txqueuelen 1000  (Ethernet)
        RX packets 1996  bytes 306274 (299.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3263  bytes 1161129 (1.1 MiB)
        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.0.0.0
        loop  txqueuelen 0  (Local Loopback)
        RX packets 466  bytes 284389 (277.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 466  bytes 284389 (277.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1500
        inet 10.22.0.1  netmask 255.255.255.0  destination 10.22.0.1
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 100  (UNSPEC)
        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

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 52:54:00:0e:5c:57  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

 

virbr0 is a libvirt managed bridge for the purposes of virtual machines that do not need connectivity from other devices on your network (read that as RDP or otherwise).  This is a bridge we plan to develop future support for inclusion in port mapping similar to how Docker works.

Link to post

Hi,

 

I'm running b15 with plus licence, and the "Check for Updates" script isn't giving me access to rc1/2.

 

I was running unRAID with Xen, so I rebooted the server w/o Xen, but still same issue.

 

Is there any way to check what might possibly go wrong? like maybe my unraid server is unable to reach LimeTech update server or something ?

 

EDIT: Ok solved, weird issue with my home router, using Google DNS in unRaid settings, and now it's working.

Link to post

Which key file should I use with rc1? I received a replacement Pro key a few weeks back from Tom which I already used with 5.x, can/should I use that or do I need to request a new Pro key from him?

 

My 5.x installation is hosed again due to an issue I had earlier, and figured I might as well upgrade to 6 now.

 

Grats on the RC! Hoping to see a step-by-step tutorial come stable release on how to upgrade, along with how to move easily to XFS.

 

Try the Upgrading to UnRAID v6 guide.  If you need something more, can you tell me what it is?

 

Wasn't aware there is such a guide, as the official wiki guide doesn't have links to that page, and googling upgrade from 5 to 6 doesn't yield that page, either. I know it's not full release, yet, but worth adding to the wiki.

 

I'll follow this. Thanks!

Link to post

Upgraded to RC1 this morning, everything running well and smoothly. The display bug for the cadvisor thumbnail is fixed.  CPU not scaling and still have the disk activity bug when going to sleep but I know these aren't on the to do list.  Just upgraded to RC2 after 12 hours on RC1 , all looking good guys!

Link to post

Which key file should I use with rc1? I received a replacement Pro key a few weeks back from Tom, can/should I use that?

The key file is tied to a particular USB stick, so you need to use the one that corresponds to the USB stick you intend to use.  This is true of all unRAID versions - not just the current rc1.
Link to post

Which key file should I use with rc1? I received a replacement Pro key a few weeks back from Tom, can/should I use that?

The key file is tied to a particular USB stick, so you need to use the one that corresponds to the USB stick you intend to use.  This is true of all unRAID versions - not just the current rc1.

 

I'm using the same USB stick as with 5.x, but obviously have to format it. Will the old key work?

Link to post

When stopping the array from the webgui, there is no status shown at the bottom of the webpage as the VMs and I assume Dockers are stopped.  It would be nice to show some kind of message as the VMs and Dockers are stopped.  It appears that the stop operation is stuck for a while.

Link to post
Guest
This topic is now closed to further replies.