New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker doesn't start on Apple silicon Macs with "Use the new Virtualization framework" option #6487
Comments
Ughh, observing the same exact problem on my 2021 M1 iMac running Monterey 12.5. |
I was having the same issue, no amount of restarting my machine or docker, or reinstalling docker fixed it. I downgraded to 4.11.1 though and now I'm able to run w/ the experimental features on. |
@jmaitrehenry, check note below the checkbox:
Did you try updating? |
Same issue for me and I'm running |
@wscourge nice to know, it was working before and I didn't see it. Also, actually, my mac doesn't see any Mac update after 12.4, I will check how I can installed them. |
After rebooting in safe mode, my Mac M1 is now able to update MacOS. After the update, I still have the issue with MacOS 12.6. I have updated the main issue with the new diagnostics. |
Same problem for me running macOS 12.6 and latest Docker Desktop 4.12 |
Just to make this clear, this is not how macOS versioning actually works. Big Sur is 11.x, Montenery is 12.x and Ventura is 13.x (not released yet). Point releases do not get distinguished names and usually they support the same hardware as previous point releases. |
@jmaitrehenry thanks for the diagnostics. I see this in the logs:
This particular issue should be fixed in the latest dev build: https://desktop-stage.docker.com/mac/main/arm64/88079/Docker.dmg Could you give that a try and let me know? If it still doesn't work, could you upload another set of diagnostics? Thanks! |
@djs55 it works with the new build! Thank you! |
It starts, but it stops faster with the new build. I am running Mac OS 13 build 22A5358e Diag ID: 45F8C6F4-01E1-45BA-AC26-DAA1AC886495/20220930053621 |
@djs55 I had the same problem, and installing the latest dev build seems to have worked for me as well. Thanks! |
@djs55 with the new build, I have a problem when I try to build to an another arch than mine when hypervisor.framework is enabled. It stop Docker Desktop and rest in a stopped state. Do you want a new issue for that? |
This issue is not limited to ARM, but the AMD64 build fixes it for Intel based Macs also https://desktop-stage.docker.com/mac/main/amd64/88079/Docker.dmg |
I just encountered the same issue. I clicked 'Cancel', then quit and relaunched Docker. |
Re-running Using M1 Max 2021 MacbookPro, macOS 12.6 |
No dice for me. Using M1 Pro 2021, MacBook Pro macOS 12.6 |
Re-running |
There hasn't been any activity on this issue for a long time. Prevent issues from auto-closing with a /lifecycle stale |
/remove-lifecycle stale |
/remove-lifecycle stale |
There hasn't been any activity on this issue for a long time. Prevent issues from auto-closing with a /lifecycle stale |
/remove-lifecycle stale |
same here on latest docker desktop (4.20?) |
@robertoandrade could you reproduce the problem then upload diagnostics and quote the ID here? Thanks! |
ok, after removing docker, all of the settings/containers via:
reinstalling docker (4.20) and enabling the options, one by one and restarting to check if it'd lock up again:
I was able to get it to start back up ok. Before that instead of getting the infinite spinning during start I was actually getting:
Everything seems ok now 🎉 |
Same error brought me here, and thanks man, it works. For me, I didn't delete the docker app. Only these two do the magic: rm -rf Library/Group\ Containers/group.com.docker
rm -rf Library/Containers/com.docker.docker It looks like somehow after macOS upgrade, it broke the docker config or something? Annnd yes, I m on |
Issue fixed for me by removing quarantine attribute for docker app by below command |
Updates from any version to 4.27.1 fixed some problems during the update process including cases where corruptions could happen. We would love your feedback and see if you encounter this issue going forward (to and from 4.27.1) Feel free to @ me in this thread if you experience this again! |
Expected behavior
Docker start
Actual behavior
Docker doesn't start
Information
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: