Docker container is unable to communicate over the VPN

I have a simple container created by:

docker run -it --rm -d -p 8080:80 --name web nginx

This is on my laptop at home. I am connected to our corporate VPN.
The resource I need my container to access is over the VPN.
My initial thought was that this shouldn’t be an issue. When the traffic leaves my container it will just use my laptops routing and figure out where to go–that seems to not be the case.
I am running wsl2 containers, I add traceroute to my container and when I to a traceroute I see:

# traceroute -I
traceroute to (, 30 hops max, 60 byte packets
 1 (  0.249 ms  0.202 ms  0.192 ms
 2 (  3152.748 ms !H  3152.713 ms !H  3152.707 ms !H

The traffic never seems to leave the container. Is this a fixable problem?
Am I running into some limitation with Docker desktop on windows?
I have tried this from more than one computer the result is exactly the same.
The container has no problem communicating with the internet but can’t seem to reach anything on the vpn.

My google searches have not turned up anything helpful.

Anyone know if this can be fixed?


So it turns out not to be a some mysterious network issue, just a simple IP conflict. Docker desktop’s implementation of kubernetes uses as it’s default IP range. This can be changed by altering the file:


The same file exists for the mac and linux but with a different path. The downside is that you may have to alter this file again after upgrading docker desktop which happens fairly often.

1 Like