-
Notifications
You must be signed in to change notification settings - Fork 122
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 Desktop 4.38.0 causing kernel panic / hard lock / reboot with macOS 15.4 Beta 1 (24E5206s) #7597
Comments
Also seeing the same. Details from the Kernel Panic: Zone info: CORE 0 recently retired instr at 0x0000000000000000 last started kext at 769244860: com.apple.filesystems.autofs 3.0 (addr 0xfffffe003e596120, size 5927) ** Stackshot Succeeded ** Bytes Traced 542560 (Uncompressed 1413984) ** Beginning dump of panic region of size 0x882f0 Beginning coredump of kernel Beginning coredump of GFX-cp |
I am also seeing this on M4 Max MacBook Pro. I think this should be treated as urgent. Seems to be an issue in Apple's end since other virtualization frameworks are also experiencing the issue. Edit: Based on user reports I've seen, it also seems to be specifically related to M4 chips. The issue is impacting OrbStack and Parallels and other virtualization frameworks too. Hopefully Apple releases an updated Beta soon. |
Yes, Seeing this also on an M4 Macbook Pro. |
Same here, my MacBook Pro M4 Pro also freezes and auto reboots on latest docker desktop arm, but my m1 Mac mini seems to be fine. Both Macs are running the latest macOS 15.4 beta 1 |
Even reinstalling docker, the problem occurs the same way. |
Adding that I'm also on an M4 Macbook Pro (Max). |
I am having the same issue. M4 Pro Mac running 15.4 Beta (24E5206s). Uninstalled docker and reinstalled latest. |
I had just gotten Docker Desktop to work correctly on my MacBook Pro with M4 Pro running macOS 15.3 (after spending 2 days troubleshooting errors preventing MS SQL Server 2022 from installing and running correctly), and OF COURSE – the same day – Apple releases macOS 15.4 and prompts me to install and reboot. I get the same issue now where trying to open Docker Desktop causes the system to crash and reboot. (Docker Desktop is version 4.38, FYI) |
I can't get it to work with any version. I have tried everything. Will this be resolved soon? I can't even find a work around to use Docker on my Mac |
From Apple's release notes: Virtual Machines Workaround: Do not launch virtual machines. If virtual machine applications launch upon login, boot to Safe Mode and disable in system settings. |
Thanks @basmilius for the links -- looks like Apple is aware of it at least and it's not just Docker but VMs in general. I'll go ahead and close this ticket. |
Does anyone have a workaround for this until Apple fixes it? I can not use Docker at all |
Description
Hello,
I've sent this over through the Feedback Assistant app as well for Apple to look into this but wanted to touch base here on Github to see if anyone might be experiencing the same thing. I have Docker run in my Login Items and my MacBook Pro M4 Max kept hard locking after trying to re-open my applications when logging in after the 15.4 Beta 1 update today. I know it's a beta so I'm used to having to deal with some issues here and there but this is the first case of a hard reboot that I've seen in many years of running Apple Developer betas.
I had to finally boot into Safe Mode and turn off Docker in my System Settings > Login Items so I could finally login. The way I discovered it was the Docker app was by trying to run each app one by one and as soon as I ran Docker, it hard locked everything and rebooted, even in Safe Mode.
Anyone else seeing this behavior? I tried downloading/reinstalling 4.38.0 from the Docker website but that didn't work.
I might try to fully get rid of all of my containers to see if it's possibly something with a particular container. I'll report back but wanted to at least get this report out there.
Thanks so much!
Reproduce
Expected behavior
No response
docker version
docker info
Diagnostics ID
55856316-3F70-48AC-AE6B-E0F8D8B03E0E/20250221204321
Additional Info
No response
The text was updated successfully, but these errors were encountered: