Registry connectivity error with 3.3.3 MacOS and new virt framework

[iben12]

• 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

login/pull/push works with 3.3.3 on Apple M1 with new virtualization framework enabled

Actual behavior

I get
Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
error. Not just docker hub, but any registry I tried.

Information

I experienced this error while on 3.3.3. Could not resolve, so I removed Docker Desktop and re-installed 3.3.1 from dmg. At the first start-up I was informed that Docker must be reset to factory settings because I had a later version installed. I agreed. Everything worked again.

I then updated to 3.3.3 via the update menu and registry connection was broken again.

I found out that disabling new virtualization framework fixes the issue.

I do not really remember ever enabling new virtualization framework, however they say that at 3.3.2 that was suggested by the application so maybe I did. Anyway, reset to factory should have disable it anyway. Or I did use 3.3.1 with the new framework without errors, but in this case this is a regression.

• macOS Version: 11.3
• Intel chip or Apple chip: Apple
• Docker Desktop Version: 3.3.3(64133)

Steps to reproduce the behavior

1. Enable new virtualization framework
2. Try to docker login or docker pull or docker push

[iben12]

Oh, just go forward to the question: I do not use VPN.

[gmsantos]

I can confirm the same problem in intel mac too, it also affects docker build; here a diagnostics to help: F423B07D-A600-4B9E-9F9E-7AFB26629699/20210511205453

[gmsantos]

As @iben12 commented, this issue wasn't present in 3.3.1. I used to build without issues. My guess it's a regression bug introduced in 3.3.3

[larseggert]

Same issue here.

[xgt001]

can confirm, same here on 3.3.3

[i2rulloa]

Same issue...

[lordgordon]

Same here, using Apple M1 and new virtualisation framework. Suggested workaround to rollback to 3.3.1 solved the issue.

macOS: 11.3.1

[gmsantos]

@lordgordon disabling new virt on 3.3.3 also works

[newmaniese]

Just putting it out, and I assume based on the change of the bug name people already know this, but this is occurring on non-M1 Macs as well.

Thanks for looking into this problem, definitely caught me off guard as I was using the new virtualization for some time.

[stefanodecillis]

Any news regarding the problem?
As said, it becomes harder to use docker without pulling images

[gmsantos]

@stefanodecillis did you disabled new virt as a workaround?

Since the new virtualization is experimental, I would not rely on it in my daily tasks.

[stefanodecillis]

@gmsantos I didn't try to be honest. It is working properly disabling the new virt even if I was hoping to use it ahaha

[stephen-turner]

@djs55 PTAL. Thanks.

[djs55]

Thanks for your reports. I recently fixed a problem in this area, could you try an experimental build?

• Apple Silicon: https://desktop-stage.docker.com/mac/stable/arm64/64397/Docker.dmg
• Intel: https://desktop-stage.docker.com/mac/stable/amd64/64397/Docker.dmg

Note I've not notarised the builds so there will probably be a warning from macOS the first time it's launched. Let me know if it works any better. If not, could you upload some diagnostics and quote the ID here? Thanks!

[iben12]

Hi @djs55,

I can confirm that on this build (3.4.0 64397) docker pull works with the new virtualization framework enabled, so it seems to fix the bug.

[iben12]

Whoever wants to try this preview build, just run:

xattr -cr /Applications/Docker.app

to un-quarantine Docker app and then you can Cancel the popup that says the application is damaged and you have to move it to the bin.

[gmsantos]

@djs55 👍 with intel build and new virt framework enabled. Thanks!

[SwenVanZanten]

Works for me too on M1 and new framework enabled 👍

[ezpuzz]

Fixed pulling on my M1, thank you @djs55

[viniciussalmeida]

Hi @djs55 it worked for me too, on Intel and new virtualization framework enabled. Thank you!

[genevera]

3.4.0 works for me

[gmsantos]

@genevera how can I get 3.4.0? It doesn't show in updates for me

[stephen-turner]

@gmsantos It's not real 3.4.0, it's the test build higher up this ticket.

[dduportal]

Same issue with 3.3.3. Worked without the new hypervisor framework.
The new dev. build is fixing the issue on my Intel mac, great job, thanks a lot folks!

[jtr109]

Thanks for your reports. I recently fixed a problem in this area, could you try an experimental build?

• Apple Silicon: https://desktop-stage.docker.com/mac/stable/arm64/64397/Docker.dmg
• Intel: https://desktop-stage.docker.com/mac/stable/amd64/64397/Docker.dmg

Note I've not notarised the builds so there will probably be a warning from macOS the first time it's launched. Let me know if it works any better. If not, could you upload some diagnostics and quote the ID here? Thanks!

It works well! Thank you very much!

[jtr109]

Hi, everyone:

The Docker Desktop noticed me to update to a new release Docker Desktop 3.4.0. But I don't see this issue motioned.

Is this problem attempted be resolved in that version? Should I update to the new version to have a try?

[gmsantos]

Updating to 3.4.0 and enabling new virt framework worked here.

[fanvinga]

Hi, everyone:

The Docker Desktop noticed me to update to a new release Docker Desktop 3.4.0. But I don't see this issue motioned.

Is this problem attempted be resolved in that version? Should I update to the new version to have a try?

New release version works for me here (Apple Silicon M1),but i don't see this issue mentioned in release note neither.

BTW my issue #5725 also has fixed and hasn't mentioned neither.

[djs55]

@gmsantos thanks for letting us know it worked for you in 3.4.

@jtr109 @fanvinga this issue should be fixed in 3.4, sorry it wasn't mentioned in the release notes. I'll close the ticket but feel free to open a new one if you experience another problem.

[jtr109]

Hi, everyone:
The Docker Desktop noticed me to update to a new release Docker Desktop 3.4.0. But I don't see this issue motioned.
Is this problem attempted be resolved in that version? Should I update to the new version to have a try?

New release version works for me here (Apple Silicon M1),but i don't see this issue mentioned in release note neither.

BTW my issue #5725 also has fixed and hasn't mentioned neither.

Hi, @fanvinga! Thanks for your reply! I will have a try on the new version.

[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