You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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 :
I get no answer from the guest VM
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)
In the meantime, some other FQDNs work from the guest VM : ......
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
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
The text was updated successfully, but these errors were encountered: