Hi, I’m using Docker version 20.10.18, build b40c2f6, on a debian desktop. I have a container creating a vpn connection, started like this: docker run -it --name vpn -h vpn --cap-add=NET_ADMIN --device /dev/net/tun vpnclient This first container gets ip 172.17.0.2 I have then a second container…

Exposed ports with net=container:

sycolth (Sycolth) September 16, 2022, 5:40pm 5

I found the problem!

Yes, the port needs to be open on the vpn container, but there’s also another change to make.

The vpn inside the container sees 172.17.0.0/16 as the local lan, so 192.168.0.0/24 is pushed over the vpn, and that’s a problem.
After I added route add -net 192.168.0.0/24 dev eth0 in the vpn container everything works.

Thanks

Docker exposed ports are not accessible from all remote networks

Topic		Replies	Views
Exposed docker ports not accessible on public IP General docker	3	3561	May 29, 2022
Docker - Forward port to host with net=container:vpn General	0	3317	September 4, 2018
Docker exposed ports are not accessible from all remote networks Compose docker , docker-compose	15	177	June 3, 2025
Container ports not accessible when using VPN Tunnel General	1	87	January 11, 2025
Windows container can't access networks visible from the host with VPN Docker Desktop	1	2628	August 19, 2020

Exposed ports with net=container:

Related topics