DNS names that can't be resolved in Colima, possibly only with gvproxy network driver

[rfay]

Description

I'm starting this issue so we can start to track down the specific DNS addresses that fail in colima/lima, and the sources of information. I get this question all the time, and tell people to use --dns 1.1.1.1 and it almost always fixes. But I think we should start to track what they are so maybe we can solve this someday.

Issue	hostname
ddev/ddev#4372	mavtek-840225427682.d.codeartifact.us-east-1.amazonaws.com
ddev/ddev#4413	www.youtube.com (seems to be youtube-ui.l.google.com)
#466 (comment)	test12345.s3.ap-northeast-1.amazonaws.com

Version

Colima Version: Various
Lima Version:
Qemu Version:

Operating System

• macOS Intel
• macOS M1
• Linux

Workarounds

Many people have reported in the comments that changing to the slirp network driver resolved the issue.

[paihu]

I have the same issue.

Reproduction Steps

1. docker network create test
2. docker run --rm -it --network test alpine
3. apk add --no-cache curl && curl test12345.s3.ap-northeast-1.amazonaws.com
4. docker network rm test

Not Reproduction Steps

1. docker network create test
2. docker run --rm -it --network test alpine
3. apk add --no-cache curl && curl test1234.s3.ap-northeast-1.amazonaws.com
4. docker network rm test

Reproduce if fqdn is more than 41 characters and non default docker network

workaround

In my case...

open ~/.colima/default/colima.yml

edit network.driver

network:
  driver: slirp

[rfay]

Added youtube.com to the list in OP

[renatho]

Added youtube.com to the list in OP

Notice that youtube.com worked for me, but www.youtube.com didn't work. 😉

[rfay]

Edited, thanks @renatho

[abiosoft]

If indeed using slirp as the network driver fixes it, this should be resolved by the next release v0.5.0.

[Schrank]

I can add sbp-plugin-binaries.s3.eu-west-1.amazonaws.com

[abiosoft]

I would like to know if this is still the case for v0.5.0.

[paihu]

Thanks.

Fixed in my environment.

[adrienthebo]

I've observed sporadic failures with golang.org; I'm running on a 2021 Mac M1 Silicon using the vz virtualization driver. This manifests when using the devcontainer cli to build workspace images.

 $ yq '.network.driver' "$(colima template --print)"
gvproxy

$ colima version
colima version 0.5.2
git commit: 6b5b6fe0540e708f0c9d6e8919fab292c671fc72

runtime: docker
arch: aarch64
client: v23.0.1
server: v20.10.20

[taylorchu]

this is still not fixed in 0.5.4