这是我的解决方案:

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}

使用docker0接口ip(比如172.17.0.1)可能是一个很好的解决方案。

只要确保您需要访问的服务侦听外部连接即可。一个典型的例子是Mysql，默认绑定到127.0.0.1，导致无法访问，直到你允许外部连接。绑定到0.0.0.0)

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.

如果你正在使用Docker Compose + Linux，你必须手动添加它(至少现在)。在docker-compose上使用extra_hosts。yaml文件:

version: '3.7'

services:

  fpm:
    build:
      context: .
    extra_hosts:
      - "host.docker.internal:host-gateway"

不要忘记更新Docker，因为这只适用于Docker v20.10+。

来源:https://github.com/docker/for-linux/issues/264#issuecomment-784985736

一种解决方案是使用特殊的容器将流量重定向到主机。您可以在这里找到这样一个容器:https://github.com/qoomon/docker-host。其思想是从容器中获取默认路由，并将其安装为传入连接的NAT网关。

一个假想的用法:

docker-host:
  image: qoomon/docker-host
  cap_add: [ 'NET_ADMIN', 'NET_RAW' ]
  restart: on-failure
  environment:
    - PORTS=999

some-service:
  image: ...
  environment:
    SERVER_URL: "http://docker-host:999"
  command: ...
  depends_on:
    - docker-host

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