IssueRaiser

Cannot access the VPN network inside a container

### Expected behavior When I'm connected through a VPN I should be able to access the VPN network inside a container. ### Actual behavior When I'm connected through a VPN I cannot access the VPN network, either by hostname or by IP. ### Information Diagnostic ID: FD552713-528B-478F-9BA6-8A6528AA18A4 <!-- - Full output of the diagnostics from "Diagnose & Feedback" in the menu ... --> ``` Docker for Mac: version: 18.03.0-ce-mac60 (dd2831d4b7421cf559a0881cc7a5fdebeb8c2b98) macOS: version 10.13.3 (build: 17D102) logs: /tmp/FD552713-528B-478F-9BA6-8A6528AA18A4/20180418-152905.tar.gz [OK] vpnkit [OK] vmnetd [OK] dns [OK] driver.amd64-linux [OK] virtualization VT-X [OK] app [OK] moby [OK] system [OK] moby-syslog [OK] kubernetes [OK] files [OK] env [OK] virtualization kern.hv_support [OK] osxfs [OK] moby-console [OK] logs [OK] docker-cli [OK] disk ``` <!-- - A reproducible case if this is a bug, Dockerfiles FTW - Page URL if this is a docs issue or the name of a man page --> ### Steps to reproduce the behavior 1. Connect to the VPN (I'm not sure which one it is, it's the client's VPN and I'm using the Pulse Secure client) 2. Start docker-compose 3. Log into a container 4. Try to connect to one of the VPN network machine, using SSH, either by hostname or by IP 5. Wait for the connection time out. ### Additional informations This was working perfectly fine when I was using Linux with

Posted by devantoine on Apr 18, 2018, 2:07 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments

github (SaaS)

Cannot access the VPN network inside a container

devantoineApr 18, 2018, 2:07 PM

### Expected behavior When I'm connected through a VPN I should be able to access the VPN network inside a container. ### Actual behavior When I'm connected through a VPN I cannot access the VPN network, either by hostname or by IP. ### Information Diagnostic ID: FD552713-528B-478F-9BA6-8A6528AA18A4 <!-- - Full output of the diagnostics from "Diagnose & Feedback" in the menu ... --> ``` Docker for Mac: version: 18.03.0-ce-mac60 (dd2831d4b7421cf559a0881cc7a5fdebeb8c2b98) macOS: version 10.13.3 (build: 17D102) logs: /tmp/FD552713-528B-478F-9BA6-8A6528AA18A4/20180418-152905.tar.gz [OK] vpnkit [OK] vmnetd [OK] dns [OK] driver.amd64-linux [OK] virtualization VT-X [OK] app [OK] moby [OK] system [OK] moby-syslog [OK] kubernetes [OK] files [OK] env [OK] virtualization kern.hv_support [OK] osxfs [OK] moby-console [OK] logs [OK] docker-cli [OK] disk ``` <!-- - A reproducible case if this is a bug, Dockerfiles FTW - Page URL if this is a docs issue or the name of a man page --> ### Steps to reproduce the behavior 1. Connect to the VPN (I'm not sure which one it is, it's the client's VPN and I'm using the Pulse Secure client) 2. Start docker-compose 3. Log into a container 4. Try to connect to one of the VPN network machine, using SSH, either by hostname or by IP 5. Wait for the connection time out. ### Additional informations This was working perfectly fine when I was using Linux with

Comments (0)

No comments yet. Start the discussion.

Comment on this issue