Using dnsHosts:host.docker.internal:host.docker.internal prevents Colima from starting

[jhberthemet]

Description

Using below config in the template prevents Colima from starting

dnsHosts:
host.docker.internal: host.docker.internal

It stays stuck here forever:

colima start
INFO[0000] starting colima
INFO[0000] runtime: docker
INFO[0000] creating and starting ... context=vm

[hostagent] hostagent socket created at /Users/jbert002/.colima/_lima/colima/ha.sock
[hostagent] Starting VZ (hint: to watch the boot progress, see "/Users/jbert002/.colima/_lima/colima/serial*.log")
[hostagent] Mounting disk "colima" on "/mnt/lima-colima"
[hostagent] Converting "/Users/jbert002/.colima/_lima/_disks/colima/datadisk" (raw) to a raw disk "/Users/jbert002/.colima/_lima/_disks/colima/datadisk"
[hostagent] [VZ] - vm state change: running
[hostagent] SSH server does not seem to be running on vsock port, using usernet forwarder

Version

colima version && limactl --version && qemu-img --version.
colima version 0.9.1
git commit: 0cbf719

runtime: docker
arch: aarch64
client: v29.1.5
server: v28.4.0
limactl version 2.0.3

Operating System

• macOS Intel <= 13 (Ventura)
• macOS Intel >= 14 (Sonoma)
• Apple Silicon <= 13 (Ventura)
• Apple Silicon >= 14 (Sonoma)
• Linux

Output of colima status

Output with fixed config:

colima status
INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: virtiofs
INFO[0000] docker socket: unix:///Users/jbert002/.colima/default/docker.sock
INFO[0000] containerd socket: unix:///Users/jbert002/.colima/default/containerd.sock

Reproduction Steps

1. colima delete
2. colima template (set dnsHosts:
   host.docker.internal: host.docker.internal)
3. colima start

It's stuck forever

Expected behaviour

I used to have below config working for years.

dnsHosts:
host.docker.internal: host.docker.internal

Additional context

No response

[abiosoft]

Why would you want to do that? That's basically an infinite dns resolution loop.

[jhberthemet]

Why would you want to do that? That's basically an infinite dns resolution loop.

It's it the way to expose host.docker.internal internally?

I used to have this config for a while and it didn't cause problem before. If it's an incorrect config then you can close this ticket.