"Docker Desktop is stopping" on macOS M1 Max and hanging #6472
Comments
|
Quick update. When I quit Docker Desktop from the menubar - the ... but it stopped at that place and has not finished still. Activity Monitor still reports a few items that have not been killed when I initiated the "Quit Docker Desktop" command.
|
|
Quick update. Starting under a separate user on the same machine didn't help. Also tried after a restart. |
|
I have the same problem. Disabling the new virtualization framework made docker for mac start again.
This fixed it, at least on my machine. |
|
Thanks @anpr. That fixed it for me too. Feel free to close this issue. |
|
Good to know. I still would like to know why this fails - I would actually prefer to use the virtualization framework. |
|
Also ran into the same issue after updating to the latest Docker Desktop. I downgraded back to 4.11.1 and the "stopping" issue disappeared and I was able to enable the virtualisation framework again. Would be great to get a solution for this. |
|
@avioli thanks for the diagnostics. The logs have something interesting: (This may be related to #6435 (comment) ) The latest development build has a fix for this issue, could you try:
If it still doesn't work, could you capture diagnostics while it's in the broken state with and quote the new ID here? Thanks! |
|
Hi, docker diagnose stops on:
stays there for more than 30 minutes... |
|
My working version stopped working when I quit Docker Desktop and shut it down. Once started later on today - it didn't become operational afterwards. @djs55 I downloaded the Apple Silicon version and replaced 85629 with the new build 86088, but I'm still get the same endless "stopping". I also got the following
I did a "Reset Docker to factory defaults", but that didn't improve anything. Diagnostics ID: F2606449-114C-4887-8E78-7926B365C0EE/20220907040930 I've removed Here's another Diagnostics ID: 6BDF8BC7-5DC2-4E87-8D86-0B8F72FC6B5C/20220907041813 |
|
@avioli thanks for trying the build and the diagnostics. Could you see if you have any Apple diagnostics reports from Docker processes (in particular |
|
There are 18 from yesterday which have the name of DiagnosticReports - 2022-09-07.zip Edit: Just a note - if these logs are generated when an executable is force-killed and not only when it crashes, then many of them will be because of that - I've force-killed them when I was wiping everything out (usually before a computer restart). Edit 2: I've also tried running Docker 4.7.11, so some of the most recent ones could be from that. |
|
@avioli thanks for the reports, they look very interesting. For the
-- it looks like it overflows the stack running a (not tail-recursive
So a very similar Edit: I think I'm building with OCaml 4.12, but there's a useful change in 4.13+: ocaml/ocaml#10549 |
In particular we would like ocaml/ocaml#10549 to make diagnosing docker/for-mac#6472 (comment) easier. Signed-off-by: David Scott <dave@recoil.org>
|
@avioli would you mind trying a development build of vpnkit for me? I've made a PR for moby/vpnkit and built it locally. I've attached the binary to this comment. It has the following shasum: It can be installed by:
Hopefully it will work better. If it doesn't, hopefully there will be an exception in the logs rather than a segfault 😅 If it fails, could you upload a diagnostic and quote the ID: (Just in case it goes wrong, it's worth looking for a new DiagnosticResport too) |
|
Just took a look at this with @djs55 and can confirm that the OCaml 4.14 build should have a better exception on the M1 Macs than the old (4.12-based) build. Linking ocaml/ocaml#10549 (comment) for the record. |
|
@djs55 🥳 The new Thank you |
|
At least on my machine, using the new vpnkit did not help for being able to active the virtualization framework again... |
|
@anpr could you upload some diagnostics and quote the ID here? Also take a look to see if there are any crash reports. There's also a known issue switching the framework on and off: perhaps try turning it on, then stopping and starting Docker (avoid the "restart" menu item, completely stop and start) |
|
I was still having issues with 4.12.0 85629. It only shows "Docker Desktop stopping..." for several minutes and nothing happens. vmnetd seems crashed and unresponsive. My problem seems to be due to blocking of the domain |
|
Experiencing the same issue here, just uploaded diagnostics: 7B32AB05-AFDB-42F9-AD70-2059500A3485/20220919085834. After replacing vpnkit as suggested above I see no improvement. Uploaded diagnostics again after this: 7B32AB05-AFDB-42F9-AD70-2059500A3485/20220919090940 What I have tried so far:
The only way for me to use Docker right now is with all the experimental features off, resulting in a very slow experience compared to using VirtioFS that I was able to use before last update. |
That ... worked for me too, this domain (sessions.bugsnag.com) is in a common kill-file I use. That's the issue, srsly? |
|
@halfpastfouram I am experiencing the same. Tried all the above but still hanging and can only run with experimental features off. |
|
I repeated my experiment @andyleanlibrary ...
Tried that twice. Repeatable. However it does not seem to be that bugsnag.com entry in particular. Removed just that one and still got the stall. |
|
For me, 4.12.0 was pretty stable, but 4.13.0 started to exhibit the issue above when I upgraded to it. |
Here it's reversed, 4.12 was having the startup issue (and only running with the DNS blocker off), while latest 4.13 is coming up fine. |
|
Just upgraded to 4.13.0 and it seems to be working fine for me. I'll keep you posted if anything changes. |
|
My trouble also seems to have been fixed in 4.13.0. |
Same here. Even after installing the development build of vpnkit from #6472 (comment) |
|
@verluci @ddbrodsky Another bit of evidence pointing to it being in the realm of a network/update issue. I am running 4.15 and have turned off Automatically check for updates and Always download updates and so far its been stable. |
💡Zscalar is also in play for me. 🤔 I'm assuming that may be why I saw the diagnostic failure captured in the screenshot I shared above. I might try disabling the checks @ianjukes mentioned to see if that stabilizes things for me as well. |
|
I've tried both Rancher desktop and colima- and both completely reset all of my configurations when a restart occurs.. it's like they have no idea that I ever configured any of my containers and the ones I have tried so far all act like they are brand new container configurations... I'll stick to and fight with Docker Desktop a bit longer.. |
@kennethredler Did disabling updates work for you? I can confirm, when I re-eneabled automatically checking for updates, that the problem returned. EDIT: I can also confirm when I disabled the automatic check for updates, Docker Desktop is completely stable again. I have a Mac Studio M1 Max running Ventura 13.1. |
It works for me 👍 |
|
Thank you @zhiweio - that's good to know. So to the Docker Desktop team: it would appear that something about the automated update process, particularly when it tries to call back across the Internet, is causing Docker Desktop to fail in certain conditions. |
Yeah, I haven't seen Docker go out to lunch since disabling auto version check. ZScalar is still in play for me, FWIW. FYI @djs55 |
|
I upgraded to v4.16.1 (95567), disabled auto version checks and downloads, and it still dies on me the same as before |
@derekperkins Do you have any extensions enabled by any chance? |
|
Yes, I had Disk Usage and Performance extensions from Docker installed and running. I just disabled extensions, so we'll see how long I go before Docker dies again. |
@derekperkins I suspect that will be the issue, as I enabled extensions and the problem returned. I think the extensions system also makes a network call back to Docker to check if there are updates to the extensions. My hunch is something is broken with the update system. I have also disabled extensions to see if its stable again. Fingers crossed! 🤞 |
|
Seems like disabling automatic updates fixed issue for me as well. |
I have Tailscale. I haven't tested yet by disabling Tailscale but putting this info just in case others have the same environment. Update: disabling automatic updates did not fix it for me. |
|
Im on a Mac Mini Intel i7 2012, disabling the update also seem to have fixed the issue for me. 🤞 Fyi: Additionally I disabled extension and everything else I don’t need lol |
|
Mac M1 Mini running Ventura 13.0.1 I'm now updating to 4.16.1 and disabling extensions...I'll report back. |
|
4.16.1 with auto-update disabled with the Portainer + Logs Explorer extensions installed works fine on Ventura 13.1 w/ Intel processor. |
|
@ianjukes 4.16.1 with extensions disabled and with auto-updates disabled still died on me today |
@derekperkins That's a real shame - I figured that would be it. Just to verify, you have uninstalled all extensions, and then unchecked the 'Enable Docker Extensions' option in the settings? I have uninstalled and disabled extensions, and I'm stable again. At least so far.
|
|
My company recently uninstalled Symantec from the mac. It's been a lot better since then but not sure if its related. |
|
@andyleanlibrary I'm at home with quite a simple network set up, and do not have any antivirus software installed. Docker should be stable. 🤷♂️ |
|
@andyleanlibrary yes, similar setup to ianjukes - domestic install without antivirus. Extensions was activated but I don't believe there were any installed at any point before I de-activated extensions - I can check later. |
|
@ianjukes thanks - good to rule it out, if only for me :-) |
|
Even with extensions disabled, mine still stoped. Ran well for 22 hours Only. I’m on 4.15.1 Apparently is supposed to be fixed in 4.16 but I have not tried it yet |
|
I'm going to close this issue because the OP reported it fixed in #6472 (comment). I'm a little worried it's becoming a basketcase of unrelated issues, which makes it hard for us to separate out who is still having problems and who's not. Docker Desktop 4.16 has some major fixes to network stability. If you're still having problems after using 4.16, please file an issue (preferably with diagnostics and/or repro steps). Thanks! |
|
FWIW, experimental features were enabled for me on 4.16.1. I don't remember enabling them recently, but it's very possible I manually did it 1+ years ago. It's now turned off to see if maybe that was causing it to crash.
|
|
@derekperkins re: "there's no repro steps other than it just dying after being open for a while." here's a good page on how to upload diagnostics when you don't have repro steps - https://docs.docker.com/desktop/troubleshoot/overview/#diagnose re: "why would you close this issue with plenty of people still reporting issues even on 4.16?" - that's a very philosophical question! why would we close one bug when there are still other bugs that cause the same symptoms? I like this old-internet post - https://www.chiark.greenend.org.uk/~sgtatham/bugs.html |
|
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. /lifecycle locked |
and others
Expected behavior
Docker Desktop starts and I can use the cli tool.
Actual behavior
I cannot run the cli tool, nor Docker Desktop is usable - it shows "Docker Desktop is stopping" and the whole UI is unusable, except for the bug report/reset tool (and various not so useful views).
Information
This behaviour is not reproducible on any other Mac computer I have access to other than the one I used to produce the diagnostics.
The problem is new - Docker Desktop used to work last week (This is Friday and today is Monday), which was running a previous version - either 4.11 or 4.7 or something close, since I did not note it except that I have a memory of seeing a version number when trying to re-install via homebrew.
The problem did not appear with an update, but with a restart of the computer and an update to the latest Docker Desktop did not resolve it.
Output of
/Applications/Docker.app/Contents/MacOS/com.docker.diagnose checkThe tool never finishes!
Steps to reproduce the behavior
I cannot provide steps, since I'm unable to reproduce it on any other machine I've got access to.
I'll create a new user account and see if Docker Desktop loads within that.
The text was updated successfully, but these errors were encountered: