in docker can't route to internet

[sheiy]

in docker can't route to the Internet but in unraid shell it works good

 

tower-diagnostics-20200306-1557.zip

[sheiy]

hello  anybody here?

[trurl]

Is it just Nextcloud or do you have other containers that also have this problem?

[sheiy]

5 minutes ago, trurl said:

Is it just Nextcloud or do you have other containers that also have this problem?

all my containers 

[sheiy]

14 hours ago, trurl said:

Is it just Nextcloud or do you have other containers that also have this problem?

Hi , all of my docker containers can't route to the Internet ,any ideas? thanks

[trurl]

Tell us more about your networking configuration.

[sheiy]

1 hour ago, trurl said:

Tell us more about your networking configuration.

[sheiy]

[bonienl]

Docker containers in different networks (one is bridge and the other one is eth0/br0) can not communicate with each other, this is a Docker restriction.

 

To make this work, the containers need to be of the same network type.

 

If you are running Unraid 6.8.2 or newer you can try to enable the setting "Host access to custom networks" and test if it works (I have never tested this, but it may work).

Edited March 7, 2020 by bonienl

[sheiy]

1 minute ago, bonienl said:

Docker containers in different networks (one is bridge and the other one is eth0/br0) can not communicate with each other, this is a Docker restriction.

 

To make this work, the containers need to be of the same network type.

I don't need docker containers  communicate with each other . My problom is my docker containers  con't route to the Internet please look 

[sheiy]

1 hour ago, trurl said:

Tell us more about your networking configuration.

I can tell you my unraid's ip username and password do you need it?

[bonienl]

5 minutes ago, sheiy said:

I don't need docker containers  communicate with each other

Sorry, I misread the openwrt VM and thought it was a Docker container.

 

A docker container on a bridge network uses address translation (NAT), that's why you see the 172.17.x.x address.

The traceroute stops after openwrt, which indicates openwrt does not forward the packets.

Check if openwrt has some firewall rule for NATed addresses in place which blocks the communication.

 

[sheiy]

59 minutes ago, bonienl said:

Sorry, I misread the openwrt VM and thought it was a Docker container.

 

A docker container on a bridge network uses address translation (NAT), that's why you see the 172.17.x.x address.

The traceroute stops after openwrt, which indicates openwrt does not forward the packets.

Check if openwrt has some firewall rule for NATed addresses in place which blocks the communication.

 

can you help me to set the openwrt config? I try and search on google but no ideas