Dial tcp: lookup auth.docker.io on [::1]:53: read udp [::1]:42878->[::1]:53: read: connection refused

Docker Hub
,
1

I’m new to the dev team and haven’t used Docker before. While I’ve been working on things so far, the team uses Docker extensively. I’m running into this error when trying to use wsl ./vendor/bin/sail up

Here is the error message am getting so far in laravel project
"failed to solve: ubuntu:22.04: failed to resolve source metadata for docker.io/library/ubuntu:22.04: failed to authorize: failed to fetch oauth token: Post : dial tcp: lookup auth.docker.io on [::1]:53: read udp [::1]:42878->[::1]:53: read: connection refused"

2

Hello

This error is not really related to docker but just means HR can’t access the image : is your internet connection is working ? Are you behind a vpn ?

Very rarely I’ve this error too (can’t access internet) and just suit and start docker again.

3

I moved your title into the content of your post and gave a shorter title. Always choose a shorter title that describes the issue and people can decide whether they can help or not. I also added code blocks

Please, format your posts according to the following guide: How to format your forum posts
In short: please, use </> button to share codes, terminal outputs, error messages or anything that can contain special characters which would be interpreted by the MarkDown filter. Use the preview feature to make sure your text is formatted as you would expect it and check your post after you have sent it so you can still fix it.

Example code block:

```
echo "I am a code."
echo "An athletic one, and I wanna run."
```
4

Hello

I am not using a VPN and my internet is perfect nothing wrong with it ?

5

Now that I looked at the first post again, it seems to me that the problem is with the name resolution and that was refused on the IPv6 loopback IP address. On Ubuntu, there is a stub resolver of systemd which is enabled by default so name resolution is done on localhost and forwarded to external DNS servers if necessary. In some cases it leads to unexpected behavior with Docker, although I haven’t seen a name resolution error when pulling an image. If you are using Ubuntu or any system that has this stub resolver enabled, you can disable it. I wrote about it here:

Just search for “stub resolver” I could be wrong, but I expected an actual DNS server IP in the error message.