Can't pull Docker Image

[riouruma]

• I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• I have uploaded Diagnostics
• Diagnostics ID:

Expected behavior

Actual behavior

Information

• macOS Version: Big Sur (M1)

Steps to reproduce the behavior

Docker

$ docker pull php:7.4-fpm
Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.64.1:53: read udp 192.168.64.3:51137->192.168.64.1:53: read: connection refused

DockerCompose

$ docker-compose build
mysql uses an image, skipping
nginx uses an image, skipping
Building php-fpm
Step 1/17 : FROM php:7.4-fpm
ERROR: Service 'php-fpm' failed to build : Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.64.1:53: read udp 192.168.64.3:58037->192.168.64.1:53: read: connection refused

[tholu]

@riouruma Did you figure out the problem? I'm experiencing the same connectivity issues with the latest tech preview.

[hcancelik]

@tholu @riouruma are you guys using Laravel Valet? or installed dnsmasq via homebrew?

[tholu]

@hcancelik Yes, Laravel Valet was indeed the problem. See laravel/valet#1031

[riouruma]

@tholu @hcancelik
No, I'm not using Laravel Valet.
I'm still facing this issues.

I often write Ruby as well, and before time I had not got errors with Docker preview.
I have got same error when I try to build image on Ruby on Rails project as well.

[riouruma]

Thanks to @hcancelik, I could pull images.

1. stop dnsmasq (brew services stop dnsmasq)
2. restart Docker Desktop
3. $ docker pull php:7.4-fpm → will success

[docker-robott]

Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

[kblcuk]

Fwiw in my case it was Use new virtualization framework experimental feature that caused this.

[djs55]

There were some fixes to the internal DNS in Docker Desktop 3.4.0 which I think should fix this issue. I'll close the ticket but if it recurs, upload a fresh set of diagnostics, quote the ID, ping me and I'll take a look / re-open the issue.

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked