what should be used instead of 'host.docker.internal' when using nerdctl in place of docker?

Question

When using docker desktop, we would connect to the host machine from the container using the URL 'host.docker.internal'.

however container is not able to connect to the host machine (i.e my machine) when I am using nerdctl instead of docker.

I installed Rancher desktop to use nerdctl

https://stackoverflow.com/users/17981939/natesh-todur had solved it in our project, I don't remember exactly the solution now — Akshay Vijay Jain, Aug 03 '22 at 16:25

Natesh Todur · Answer 1 · 2022-08-04T06:42:26.800

2

ipconfig getifaddr en0

The above command will give the IP address of your wireless connection. Note, this will only work for MacOS. This IP can then be written to the /etc/hosts of your container against host.docker.internal as they share the same network. This can help the container communicate to the host machine by using host.dock.internal . Although, an elegant solution is expected from RancherDesktop (or its already available in the newer versions).

edited Aug 04 '22 at 06:42

answered Aug 04 '22 at 06:37

Natesh Todur

21
3

Thanks Natesh and Akshay. Natesh I'm assuming you used dockerd only..right? – Kaneki21 Aug 05 '22 at 04:15
dockerd (moby) as the container runtime. – Natesh Todur Aug 16 '22 at 09:28

score 1 · Answer 2 · answered Mar 12 '22 at 00:10

From lima docs.

The loopback addresses of the host is 192.168.5.2 and is accessible from the guest as host.lima.internal.

So instead of host.docker.internal, provide 192.168.5.2

I have tested this with nerdctl distributed via Rancher and it works!

reference: https://github.com/lima-vm/lima/blob/master/docs/network.md

what should be used instead of 'host.docker.internal' when using nerdctl in place of docker?

2 Answers2

Linked