blocks|key|522388|text|不确定这是否是最好的解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|522389|我使用了连接到VPN后出现在主机上的DNS。|522390|scutil+--dns+%7C+grep+'nameserver\[[0-9]*\]'
nameserver[0]+:+xxx.xxx.xxx.xxx|code-block|syntax|javascript|522391|修改后的停靠程序运行命令：|522392|docker+run+--cidfile="docker.pid"+--dns=xxx.xxx.xxx.xxx+--publish-all|522393|现在码头容器可以访问VPN背后的资源.很管用，但我不知道是好是坏.|522394|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Not sure if it's best solution. 

I took DNS that appears on my host after connecting to VPN

<pre><code>scutil --dns | grep 'nameserver\[[0-9]*\]'
nameserver[0] : xxx.xxx.xxx.xxx
</code></pre>

Modified docker run command: 

<pre><code>docker run --cidfile="docker.pid" --dns=xxx.xxx.xxx.xxx --publish-all
</code></pre>

Now docker container can access resources behind VPN... It works, but I have no idea if it's good or bad...

blocks|key|2394732|text|在将主机连接到VPN后，我不得不重新启动docker。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2394733|sudo+systemctl+restart+docker+docker+start+{name-of-container}|offset|length|style|CODE|2394734|entityMap^0|0|0|1Q|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I had to restart docker after connecting host machine to VPN.

<code>sudo systemctl restart docker
docker start {name-of-container}</code>

blocks|key|613133|text|我确实有这个问题。我尝试了这里提出的其他解决方案，但它们对我没有用。经过多次尝试和错误之后，这个解决方案很好地工作了：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|613134|在daemon.json配置文件中添加"bip"："192.168.1.5/24“。这个文件可以在docker或at+/etc/+docker+/daemon.json下的docker桌面设置中找到。BIP是桥接IP地址的设置，它将更改其子网中的IP对接者分配。通过更改此设置，我避免了VPN和停靠ip地址之间的冲突。|613135|重新启动停靠守护进程。|613136|停止所有集装箱。|613137|运行“停靠网络剪枝”以删除未使用的网络。|613138|重新启动所有容器。这将用新的IP地址重新创建他们的网络。|613139|在将来连接到VPN之后，您可能仍然需要重新启动码头。有关其他解决方案和想法，请参阅此线程：https://github.com/docker/for-mac/issues/2820|offset|length|613140|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/docker/for-mac/issues/2820^0|0|0|0|0|0|0|19|19|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@]|9|@$N|14|O|15|1|16]]|A|$]]|$1|P|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]]]

I had this exact problem. I tried other solutions suggested here, but they didn't work for me. After a lot of trial and error this solution worked very nicely:
Add &quot;bip&quot;: &quot;192.168.1.5/24&quot; to the daemon.json configuration file. This file can be found in the docker desktop settings under docker engine or at /etc/docker/daemon.json. BIP is the setting for bridge IP addresses and will change the IPs docker assigns in its subnet. By changing this setting I avoided conflicts between VPN and docker ip addresses.
Restart docker daemon.
Stop all containers.
Run ‘docker network prune’ to remove unused networks.
Restart all containers. This will recreate their networks with the new IP addresses.
You may still need to restart docker after connecting to the VPN in the future. See this thread for other solutions and ideas: <a href="https://github.com/docker/for-mac/issues/2820" rel="noreferrer">https://github.com/docker/for-mac/issues/2820</a>

blocks|key|2394727|text|也有类似的问题。OP的解决方案起了作用，但简单地重新启动我的停靠程序vm也是如此：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2394728|docker-machine+restart+$host|code-block|syntax|javascript|2394729|灵感：no/|offset|length|2394730|entityMap|0|LINK|mutability|MUTABLE|url|https://www.reddit.com/r/docker/comments/39z4xd/when_my_docker_host_is_connected_to_vpn_i_can_no/^0|0|0|3|3|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

Had a similar problem. OP's solution worked, but so did simply restarting my docker vm:

<pre><code>docker-machine restart $host
</code></pre>

Inspiration: <a href="https://www.reddit.com/r/docker/comments/39z4xd/when_my_docker_host_is_connected_to_vpn_i_can_no/" rel="noreferrer">https://www.reddit.com/r/docker/comments/39z4xd/when_my_docker_host_is_connected_to_vpn_i_can_no/</a>

blocks|key|522524|text|在Mac上运行的docker版本3.6.0+(67351)中有此问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|522525|对我有用的是结合@Sheridan+Rea和@Marco发布的解决方案。|522526|将Docker子网更改为192.168.65.0/28.它被设定在192.168.63.0/24之前。单击应用&重新启动/重新启动码头|ordered-list-item|offset|length|style|BOLD|522527|运行docker+network+prune|CODE|522528|运行docker+compose+up|522529|简单地改变Docker子网对我没用|522530|现在我可以在VPN后面平IP地址了。|522531|entityMap^0|0|0|C|F|0|2|K|0|2|H|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|X|8|@$G|Y|H|Z|I|J]]|9|@]|A|$]]|$1|K|3|L|5|F|7|10|8|@$G|11|H|12|I|M]]|9|@]|A|$]]|$1|N|3|O|5|F|7|13|8|@$G|14|H|15|I|M]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|16|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|17|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|U|$]]

Had this issue on docker version 3.6.0 (67351) running on Mac
What worked for me is combining the solutions posted by @Sheridan Rea and @Marco
<ol>
<li>Changed Docker subnet to 192.168.65.0/28. It was set to 192.168.63.0/24 before. Clicked Apply &amp; Restart / Restart Docker
</li>
<li>Run <code>docker network prune</code>
</li>
<li>Run <code>docker compose up</code>
</li>
</ol>
Simply changing Docker subnet didn't worked for me
Now I can ping IP addresses behind VPN

blocks|key|2394751|text|对我来说起作用的是将对接子网掩码从/24更改为/28，然后重新启动，我现在可以在我的vpn网络上进行ping、telnet和其他事情了。它说默认情况下是/28，但docker桌面附带了/24。也许是打错了，我不知道。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2394752|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

What worked for me was to change docker subnet mask from /24 to /28, then restarted and I can now ping, telnet and other things on my vpn network. It says the default is /28 but docker desktop ships with /24 on it. Maybe it's a typo, I don't know.

blocks|key|522556|text|不知道为什么，但正如其他人所建议的，更改Docker子网是有效的。唯一的区别是，在DockerDesktopforWindowsv4.14.0上，将子网设置为/28不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|522557|​|522558|📷|atomic|offset|length|522559|522560|但是，仅仅从192.168.65.0/24到192.168.66.0/24之间的子网IP地址就起了作用。|522561|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/0780c652324aa5f98c90a9f2c0e89b0e.png|imageAlt^0|0|0|0|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@$G|X|H|Y|1|Z]]|A|$]]|$1|I|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S|T|-4]]]]

Not sure why, but as others have suggested here changing Docker subnet worked.
The only difference is that on Docker Desktop for Windows v4.14.0 setting subnet to /28 was not working.
<a href="https://i.stack.imgur.com/qwxwg.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/qwxwg.png" alt="screeshot of error message" /></a>
But just bumping the subnet IP addess from 192.168.65.0/24 to 192.168.66.0/24 did the trick.

blocks|key|613314|text|在MacOS和OpenVPN客户机上，之前发布的解决方案都没有对我起作用。我想我只需要像这样定义extra_hosts：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|613315|version:+"3.9"
services:
++++app:
++++++++extra_hosts:
++++++++++++-+"something.vpn:192.168.196.3"|code-block|syntax|javascript|613316|现在访问码头集装箱内的something.vpn导致192.168.196.3。没有必要更改停靠子网或其他任何内容。|613317|entityMap^0|1C|B|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

Neither of the previously posted solutions worked for me on MacOS with OpenVPN client. I figured I only need to define <code>extra_hosts</code> like this:
<pre><code>version: &quot;3.9&quot;
services:
 app:
 extra_hosts:
 - &quot;something.vpn:192.168.196.3&quot;
</code></pre>
Now accessing something.vpn inside Docker container leads to 192.168.196.3. There was no need to change docker subnet or anything else.

blocks|key|2394934|text|使用docker+run+--net+nat对我起了很大的作用。这是针对在桌面的上运行的Windows容器的(Windows)|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2394935|entityMap^0|2|K|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Using <code>docker run --net nat</code> did the trick for me.
This was for a Windows container running on Docker for Desktop (Windows)

I'm trying to run docker image on MacOS with VPN turned on (TUN device). Docker container can access internet, but is not able to access resources behind vpn. What is the right way to make Docker go to VPN network?

I've tried
<code>docker run --net host</code> to make docker share host network, it didn't help. 
Host can access VPN resources, docker container can't resolve their names..

Docker container and host network VPN

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正试图在MacOS上运行对接映像，并打开(TUN设备)。Docker容器可以访问internet，但无法访问vpn背后的资源。什么是正确的方式使码头进入VPN网络？我试过docker run --net host让码头共享主机网络，但没有帮助。主机可以访问VPN资源，码头容器不能解析它们的名称。

问码头集装箱与主机网络VPN
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问码头集装箱与主机网络VPNEN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问码头集装箱与主机网络VPN
EN