Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DNS resolution issues #1260

Open
1 of 5 tasks
AnthoBalitrand opened this issue Jan 28, 2025 · 0 comments
Open
1 of 5 tasks

DNS resolution issues #1260

AnthoBalitrand opened this issue Jan 28, 2025 · 0 comments

Comments

@AnthoBalitrand
Copy link

AnthoBalitrand commented Jan 28, 2025

Description

I have DNS resolution issues from my colima VM for some time now (seems to be since last upgrade).

Example :
While I'm able to resolve registry-1.docker.io from the host :

Server:		192.168.6.193
Address:	192.168.6.193#53

Non-authoritative answer:
Name:	registry-1.docker.io
Address: 98.85.153.80
Name:	registry-1.docker.io
Address: 44.208.254.194
Name:	registry-1.docker.io
Address: 3.94.224.37

I get no answer from the guest VM

; <<>> DiG 9.18.30-0ubuntu0.24.04.1-Ubuntu <<>> registry-1.docker.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 52058
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;registry-1.docker.io.		IN	A

;; Query time: 3004 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Tue Jan 28 18:50:34 CET 2025
;; MSG SIZE  rcvd: 49

As a result, no images can be downloaded (but it also impacts DNS generally, so impacting all containers service as soon as they need internet access)

docker container run --rm -it --name dns-test alpine sh
Unable to find image 'alpine:latest' locally
docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io on 127.0.0.53:53: no such host.
See 'docker run --help'.

In the meantime, some other FQDNs work from the guest VM : ......

; <<>> DiG 9.18.30-0ubuntu0.24.04.1-Ubuntu <<>> auth.docker.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50208
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;auth.docker.io.			IN	A

;; ANSWER SECTION:
auth.docker.io.		41	IN	A	3.94.224.37
auth.docker.io.		41	IN	A	44.208.254.194
auth.docker.io.		41	IN	A	98.85.153.80

Version

colima version 0.8.1
git commit: 96598cc

runtime: docker
arch: aarch64
client: v27.3.1
server: v27.4.0
limactl version 1.0.3
qemu-img version 9.2.0
Copyright (c) 2003-2024 Fabrice Bellard and the QEMU Project developers

Operating System

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

Output of colima status

INFO[0000] colima is running using QEMU
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] socket: unix:///Users/to148757/.colima/default/docker.sock

Reproduction Steps

Expected behaviour

No response

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant