tnerb

I agree it does appear that way. Not sure how that is happening... I thought dockers were separated. They are. You sure you not got something going on at the router level? Or any other openvpn plugin? Spent some time this morning confirming I don't have anything else connecting to OpenVPN in the network. If I stop the transmission-openvpn docker then duckdns updates the correct external IP. Setting the duckdns docker to Host and Privileged does nothing. This is very confusing to me. Host mode won't do anything. That's only for incoming connections. You can exec into the container and do traceroute to confirm but it's most definitely an issue with openvpn. Nothing we can do in the duckdns side Thanks a lot for looking into it and responding. I'll have to do some more digging. I'll look into what you suggested with the traceroute.

I agree it does appear that way. Not sure how that is happening... I thought dockers were separated. They are. You sure you not got something going on at the router level? Or any other openvpn plugin? Spent some time this morning confirming I don't have anything else connecting to OpenVPN in the network. If I stop the transmission-openvpn docker then duckdns updates the correct external IP. Setting the duckdns docker to Host and Privileged does nothing. This is very confusing to me.

I agree it does appear that way. Not sure how that is happening... I thought dockers were separated.

Where does the docker get the IP from? I'm having an issue where it is grabbing the IP used by my VPN service (PIA) that i connect with my transmission-openvpn docker to. If I stop the transmission-openvpn docker the duckdns docker updates the duckdns.org service with my outward facing IP. Any thoughts how I can run the duckdns docker to update with my IP (not the PIA ip)? I've tried running it as a host and bridge network type.

Thank you very much for you help. I ended up not having to "nuke" my docker image. Between clearing out my network settings and updating my motherboard firmware it is working now cheers

I haven't. I'm not clear on what that entails. Will I lose all my data for my dockers? (plex, Sonarr, etc) Thanks

looks like I'm having issues connecting. Not using jumbo frames. MTU set to default on router and unraid (I assume this is 1500). Any thoughts on what could be causing this? Attached diagnostics zip file. ..... time="2016-12-04T15:29:32.703278692-05:00" level=info msg="Loading containers: done." time="2016-12-04T15:29:32.703308006-05:00" level=info msg="Daemon has completed initialization" time="2016-12-04T15:29:32.703344085-05:00" level=info msg="Docker daemon" commit=ceb0ccd-unsupported execdriver=native-0.2 graphdriver=btrfs version=1.10.3 time="2016-12-04T15:29:32.711001588-05:00" level=info msg="API listen on /var/run/docker.sock" time="2016-12-04T19:53:07.029826300-05:00" level=warning msg="Error getting v2 registry: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" time="2016-12-04T20:06:31.791605844-05:00" level=warning msg="Error getting v2 registry: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" time="2016-12-04T20:12:24.624348545-05:00" level=warning msg="Error getting v2 registry: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" time="2016-12-04T20:48:24.231001470-05:00" level=warning msg="Error getting v2 registry: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" time="2016-12-06T17:07:36.259546582-05:00" level=warning msg="Error getting v2 registry: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" time="2016-12-11T00:02:46.633080856-05:00" level=warning msg="Error getting v2 registry: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" time="2016-12-11T00:03:34.229118742-05:00" level=warning msg="Error getting v2 registry: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" time="2016-12-11T00:04:21.771048382-05:00" level=warning msg="Error getting v2 registry: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" time="2016-12-11T00:05:09.396748691-05:00" level=warning msg="Error getting v2 registry: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" time="2016-12-11T12:37:20.924071208-05:00" level=info msg="Processing signal 'terminated'" time="2016-12-11T12:44:58.243095601-05:00" level=info msg="Graph migration to content-addressability took 0.04 seconds" time="2016-12-11T12:44:58.250268661-05:00" level=info msg="Firewalld running: false" time="2016-12-11T12:44:58.454884278-05:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address" time="2016-12-11T12:44:58.617108245-05:00" level=info msg="Loading containers: start." ....... h340-diagnostics-20161211-1604.zip

6.2.4 Upgraded when I first discovered the issue, thought it might be a contributer. No tips and tweaks plug-in. I think I need to nuke my network settings and start over. Annoying to stop the array for that though.

Unsure how to check for jumbo frames but I don't believe I have enabled that anywhere (router or unraid). I have a static IP, set the default gateway and ISP DNS addresses and 8.8.8.8 added as a third. h340-diagnostics-20161206-1709.zip

Any resolution to your error? I'm getting this for every docker I try to update or install.

I agree the information is quite good. I find I learn a lot from reading forum posts as well, ended up getting more confused.

Darn. Will VNC performance be terrible? Thanks for the replies, I'll pursue adding a small video card as both my case and power supply are quite small.

Trying to understand how to setup a VM is confusing me a fair bit. A lot of the information in the forum seems outdated. I have a ASRock H170m-ac motherboard with a i5-6500, 16gb ram, 120gb ssd. My array is currently made up of a 1TB, 3TB and soon a 4TB parity drive. I currently do not have a video card installed. Is it possible to run a VM (linux mint or ubuntu) using the integrated graphics provided by the CPU/motherboard? I currently have a monitor connected to the DVI port displaying the output of unraid (root login). I don't need the VM to be very powerful, mostly web browsing. Mostly want to stop using my laptop as a desktop computer. thoughts?