Docker Community Forums

Share and learn in the Docker community.

Docker containser has not access to external resources behind a VPN

Hello All,

I’m trying to connect with an external system which is behind a VPN, but I cannot reached it from the container (I’m trying to access using the ip directly).

I tried to restart the docker engine after connect the host with the VPN, but this doesn’t work.

Any suggestion about what could be my problem?

Host environment:

  • Ubuntu
  • Release 19.10
  • Codename: eoan

Docker version:

  • 19.03.8, build afacb8b7f0
1 Like

I think I also have a similar issue.
When using a pulse secure VPN, my docker containers lose their connectivity to external domains(public domains like google.com). That may have something to do with how the VPN rewrites the routing table, perhaps breaking the routing rules put in place by docker.

Also, I’m running in docker swarm mode.
How about you?

Environment:

# uname -a
Linux R90R4K4C 5.4.7-050407-generic #201912311234 SMP Tue Dec 31 17:38:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

# docker version
Client: Docker Engine - Community
Version: 19.03.8
API version: 1.40
Go version: go1.12.17
Git commit: afacb8b7f0
Built: Wed Mar 11 01:25:46 2020
OS/Arch: linux/amd64
Experimental: false

Server: Docker Engine - Community
Engine:
Version: 19.03.8
API version: 1.40 (minimum version 1.12)
Go version: go1.12.17
Git commit: afacb8b7f0
Built: Wed Mar 11 01:24:19 2020
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.2.13
GitCommit: 7ad184331fa3e55e52b890ea95e65ba581ae3429
runc:
Version: 1.0.0-rc10
GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd
docker-init:
Version: 0.18.0
GitCommit: fec3683