This message was deleted.

Hmm, anything interesting in

/var/log/docker.log

in the VM (get there via

rdctl shell

)? When I set up an invalid registry mirror, it does appear to do something:

time="2023-06-20T23:12:27.604932476Z" level=warning msg="Error getting v2 registry: Get \"<https://nowhere.invalid/v2/>\": dial tcp: lookup nowhere.invalid on 192.168.5.3:53: lame referral"
time="2023-06-20T23:12:27.604981227Z" level=info msg="Attempting next endpoint for pull after error: Get \"<https://nowhere.invalid/v2/>\": dial tcp: lookup nowhere.invalid on 192.168.5.3:53: lame referral"

So it's at least being picked up. (I don't have a mirror locally, so of course if fails… I can try to set up a mirror locally and do a more detailed test if we can at least narrow down where the error is a bit first.)

There is no

/var/log/docker.log

inside the wsl VM. Also, there is no log entry for quay in

%LOCALAPPDATA%\rancher-desktop\logs

.

Ah, this is Windows. Yeah, that's where the docker log is, but I still see the same:

time="2023-06-21T22:27:25.478042301Z" level=warning msg="Error getting v2 registry: Get \"<https://nowhere.invalid/v2/>\": dial tcp: lookup nowhere.invalid on 192.168.127.2:53: read udp 192.168.127.2:34291->192.168.127.2:53: i/o timeout"
time="2023-06-21T22:27:25.480336401Z" level=info msg="Attempting next endpoint for pull after error: Get \"<https://nowhere.invalid/v2/>\": dial tcp: lookup nowhere.invalid on 192.168.127.2:53: read udp 192.168.127.2:34291->192.168.127.2:53: i/o timeout"

Can I confirm that I'm checking the right thing?

> rdctl shell cat /etc/docker/daemon.json
{"registry-mirrors":["<https://nowhere.invalid>"]}

Yes, registry-mirrors and insecure-registries are correctly set. Not eure, moby supports this.