tldr;通过静态IP 172.17.0.1访问主机

对主机进行HTTP请求:

IP addr show | grep "\binet\b.执行以下命令获取静态IP地址。* \ bdocker0 \ b”| awk的{打印$ 2}| 1 - d ' / ' - f 添加新的IP到允许的主机 使用刚刚在请求中找到的IP地址:req = requests.get('http://172.17.0.1:8000/api/YOUR_ENDPOINT')

这取决于你想做什么。如果您使用——net=host运行，那么localhost应该可以正常工作。如果使用默认网络，请使用静态IP 172.17.0.1。我怀疑这两个领域的表现都不会与那些领域完全相同。

这是我的解决方案:

IP_ADDRESS=$(ip addr show | grep "\binet\b.*\bdocker0\b" | awk '{print $2}' | cut -d '/' -f 1)

然后在docker-compose中:

extra_hosts:
  docker.host: ${IP_ADDRESS}

host.docker.internal exists only in Windows WSL because Docker Desktop for Windows runs Docker daemon inside the special WSL VM Docker-Desktop. It has its own localhost and its own WSL2 interface to communicate with Windows. This VM has no static IP. The IP is generated every time when VM is created and passed via host.docker.internal in the generated /etc/hosts to every distro. Although there is no bridge or real v-switch all ports opened on eth0 of VM internal network are mapped on the host Local network, BUT NOT ON THE ETH0 OF THE HOST. There is no real bridge and port mapping - nothing to configure. Inside WSL VM its Localhost is the same as the localhost of the Linux machine. 2 processes inside WSL VM can communicate via localhost. Cross-distro IPC must use host.docker.internal. It is possible to create bridge inside WSL VM -Docker does it.

对于linux，我可以使用我试图连接到的服务名，例如，我的一个容器(php-fpm)试图连接到mysql，所以我使用mysql作为主机名，因为这是我的docker-compose中的服务名

tldr;通过静态IP 172.17.0.1访问主机

对主机进行HTTP请求:

IP addr show | grep "\binet\b.执行以下命令获取静态IP地址。* \ bdocker0 \ b”| awk的{打印$ 2}| 1 - d ' / ' - f 添加新的IP到允许的主机 使用刚刚在请求中找到的IP地址:req = requests.get('http://172.17.0.1:8000/api/YOUR_ENDPOINT')