I have tried disabling enabled experimental features.I have tried with the latest version of Docker Desktop.
Once I find a simple way to recreate the docker exec -d bug I'm experiencing, I'll create another issue and link it here as well. My assumption is that despite how I configure it on my M1 Mac, it never actually changes and instead just uses the newer virtualization framework. Disabling this option on the M1 Mac does nothing, and the bug remains. When disabling the new virtualization framework on the Intel Mac, the bug goes away. I raise this because I'm experiencing a bug with docker exec -d on both an M1 Mac as well as an Intel Mac that had the 'Use new Virtualization framework' checked. By this, I assume they originally meant the Big Sur virtualization framework, which would imply the old virtualization framework should not even be an option. TLDR: It is my understanding that M1 Macs don't even have the option for using the old virtualization framework, so don't even expose it as an option under Experimental Features.ĭocker has previously indicated that Docker for Mac on M1-based Macs would 'move onto Apple’s new hypervisor framework'.
