host.docker.internal support (on MacOS)

[derkoe]

We have some applications that use host.docker.internal with docker-compose.yml in the configuration.

How can I support this in Podman Desktop on MacOS?

[benoitf]

Hello @derkoe

you can use host.containers.internal instead for now.

and you could follow containers/podman#19361 about having the docker hostname being supported directly

[derkoe]

you can use host.containers.internal instead for

We have people in the team using Docker - so, we have to keep host.docker.internal in the config files.

containers/podman#19361

looking forward to this

[benoitf]

Maybe add an extra host in case of podman (setting host.docker.internal using host.containers.internal value) (for experimenting)

[derkoe]

Yes, that would work but only with a static IP (which may change per network).

host-gateway is also not working in podman containers/podman#14390

[benoitf]

for host-gateway it should land in Podman 4.7.0 as it seems this enhancement has been merged containers/common#1549

[derkoe]

BTW this is not fixed in Podman 4.7 for Mac because this commit did not make it: containers/podman@58b5ae2

A workaround is to manually download a new version of gvproxy and replace it in your installation

[derkoe]

To summarize the comments:

• Currently, host.docker.internal is not supported in Podman
• There is an open feature request in Podman for this: Add 'pre-defined/reserved' internal hostnames podman#19361
• You will be able to add custom host mappings with host-gateway starting with Podman 4.7.0 (see Support special IP designator host-gateway in --add-host. podman#14390 and libnetwork: Add support for host-gatway common#1549). This can be used to create a mapping for host.docker.internal