-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not work on Unraid NAS (Slackware) #26
Comments
Yeah, I was a little quick there. Compared to the log from your Rpi. But I get what you're saying about the 172.17.42.1 address. See the first section here https://docs.docker.com/articles/networking/ about the default docker0 interface. Also see the part about the --bip flag, maybe you could try to set it to 172.17.42.1/16 or try something else. See if that affects the interfaces or routing. |
I have posted on Unraid forums to understand the network options under the platform, but the summary is that if I select Bridged network, I get port mapping but no docker0: interface with a 172.x.x.x address. If I select Host, apparently all ports are opened to the container. When I tried that I got an error with the routing:
Here are my interfaces in the Host network config:
|
Bridgded mode is default for Docker, ref: https://docs.docker.com/articles/networking/#container-networking Reading that section I also think it's weird that bridged mode wont give you the docker0 interface as docker0 is the bridge interface. Can you check the settings of your docker daemon? On ubuntu there's a file used by Upstart called /etc/default/docker that contains default parameters for the daemon. Maybe you could give it some other DOCKER_OPTS from the networking section. This seems to be all about the docker daemon and its networking behavior on the Unraid system. You might have to do some digging and exploring of other docker networking options. |
Apologies but I am swamped with family demands and travels! Here is the file, it's empty really:
I am investigating a new docker after being told somebody had built a OpenVPN & (unfortunately) Deluge server, just to see differences with yours, but I think that the little time I could afford to look, it's clear that this image sets an IP and play with routing tables, not that I understand everything that is being done with those... Here is a link if you are interested in an alternative: https://hub.docker.com/r/binhex/arch-delugevpn/ I am struggling to set it up but as soon as I get the config right I will report back |
Here is my log, it seems to be very similar to yours, I am not sure what you meant when you said that my routing seem be done differently on Unraid? I am clueless when it comes to routing but I am puzzled by that 172.17.42.1 address as my docker eth0 address is actually 172.17.0.68 (see me interfaces below)
Here are my routes
and my interfaces
The text was updated successfully, but these errors were encountered: