Docker on OSX (Big Sur) causes kernel panics and reboots the system when waking from sleep

Docker Desktop for Mac
1

mirrored here.: Docker for OSX will kernal panic my (Big Sur) Mac book pro when waking from sleep. · Issue #5715 · docker/for-mac · GitHub

Expected behavior

If my laptop were to go to sleep, when I wake it, it won’t report a kernel panic and have completely restarted.

Actual behavior

Almost consistently, if I let my laptop sleep with Docker running, waking it from that sleep, will result in a kernel panic and a restart of the whole system.

Information

  • macOS Version: Big Sur 11.3.1 (20E241)
  • Intel chip or Apple chip: Intel i9 8 core 2.4ghz
  • Docker Desktop Version: 3.3.3 (64133)

Steps to reproduce the behavior

  1. start the computer, start docker, do work… walk away from it to get coffee, feed the pets, ponder life and the meaning of it all?
  2. Return to computer, with enough time having past for the computer to go to full sleep. Attempt to wake it.

Here is a very common crash dump from the OS

panic(cpu 0 caller 0xfffffff020157448): x86 CPU CATERR detected
Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 18P4556
macOS version: 20E241
Kernel version: Darwin Kernel Version 20.4.0: Thu Mar  4 23:34:36 PST 2021; root:xnu-7195.101.1~1/RELEASE_ARM64_T8010
Kernel UUID: 3FA744A7-0F34-36DA-AA6D-F6503A3176ED
iBoot version: iBoot-6723.101.4
secure boot?: YES
x86 EFI Boot State: 0x16
x86 System State: 0x0
x86 Power State: 0x0
x86 Shutdown Cause: 0xec
x86 Previous Power Transitions: 0x40001000100
PCIeUp link state: 0x89473611
Paniclog version: 13
Kernel slide:      0x000000001820c000
Kernel text base:  0xfffffff01f210000
mach_absolute_time: 0x1a00d3e7728
Epoch Time:        sec       usec
  Boot    : 0x60aaf39b 0x00024c40
  Sleep   : 0x60ab4052 0x0005aadc
  Wake    : 0x60ab4856 0x000e04c9
  Calendar: 0x60ac1e7a 0x000bd641

Panicked task 0xffffffe199de0630: 3352 pages, 226 threads: pid 0: kernel_task
Panicked thread: 0xffffffe199fdf200, backtrace: 0xffffffe804343700, tid: 406
		  lr: 0xfffffff01f95342c  fp: 0xffffffe804343750
		  lr: 0xfffffff01f953284  fp: 0xffffffe8043437c0
		  lr: 0xfffffff01fa7e938  fp: 0xffffffe804343890
		  lr: 0xfffffff01ff755fc  fp: 0xffffffe8043438a0
		  lr: 0xfffffff01f952fb8  fp: 0xffffffe804343c20
		  lr: 0xfffffff01f952fb8  fp: 0xffffffe804343c80
		  lr: 0xfffffff020973200  fp: 0xffffffe804343ca0
		  lr: 0xfffffff020157448  fp: 0xffffffe804343cd0
		  lr: 0xfffffff0201457d8  fp: 0xffffffe804343d30
		  lr: 0xfffffff0201476d4  fp: 0xffffffe804343dc0
		  lr: 0xfffffff020144e7c  fp: 0xffffffe804343e50
		  lr: 0xfffffff02004a4c4  fp: 0xffffffe804343e80
		  lr: 0xfffffff01fecc90c  fp: 0xffffffe804343ec0
		  lr: 0xfffffff01fecc18c  fp: 0xffffffe804343f00
		  lr: 0xfffffff01ff805a0  fp: 0x0000000000000000
2

Same problem here. Started happening a few weeks ago. Uninstalled Docker and no more kernel panics since then.

Did you have this solved in some way or just gave up using docker on your mac?

Docker on Mac actually runs a Ubuntu VM and then hosts the containers inside it. It seems the VM is causing a kernel panic on MacOS.

3

Not a solution, but still in case it helps: I am using Docker on two instances of macOS 11.4 Big Sur (20F71), and am not seeing these problems.

4

I have the same problem on my m1 macbook pro. After analysing the logs I got to know its docker and surprised to see your thread. I am going to uninstall it.

5

Hi agentsan, how did you determine that the cause of the problem was docker? What analysis did you do on the logs? What did you fild/search for? I am trying to do such an analysis, but I am not finding any evidence.