Docker Desktop 4.7 Stops working, suddenly. Frozen containers.

[jrppl-dev]

• [ x I have tried with the latest version of Docker Desktop
• [x ] I have tried disabling enabled experimental features
• I have uploaded Diagnostics
• Diagnostics ID:

Expected behavior

I expected to not have docker freezed ! 👍

Actual behavior

Docker freezes randomly. I cannot work like this. I'm having this issue on several docker desktop versions, 4.5, 4.6 and now on 4.7.

My Docker Environment:

Docker version 20.10.14, build a224086
docker-compose version 1.29.2, build 5becea4c
Docker Desktop: 4.7
Mac Version: 12.3.1
Enabled Experimental Features

Output of /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check

docker.log

Steps to reproduce the behavior

[riki137]

Happens to me too, same versions as described above.

Also had this problem on 4.5.0, 4.6.1 and now 4.7

[nickjj]

I've seen 2 reports of this with folks using macOS 12.3.X and Docker Desktop 4.6.X / 4.7.0 along with Intel MBPs. Experimental virtiofs was enabled in both cases. I don't have enough data to say if this happened with 4.4.X or 4.5.X too.

They reported this as containers were hanging and became unresponsive. Restarting was the only way to fix it and it happened often enough to be disruptive for work.

[jrppl-dev]

I've this issue on version 4.5, 4.61 and now also on 4.7. I also confirm It's impossible to work, with this happening.
What i've done was to disable experimental features, It was still happening even with those disabled. Every frozen containers I needed to do down and up, most of the times docker was frozen in order to make it work i needed to open mac task manager and force kill every docker process and start again docker. Then Without any reason, It start to work normally.

. - since on the updates apple updated the docker engine and Kernel, I also rebuild all the containers, and same result. If you are at 4.5 please DO NOT update to 4.6 or 4.7. it will broke your docker. Then even downgrade will not help. .

My first question is...why a unix system needs virtualization?? Only Apple do stuff like this. What I recommend....just use a OS that works , designed for productivity and stable...who know which one is?? Yup Ubuntu with i3.

If you are stuck like me by the company who forces to use mac...through it against a wall and say it slipped from your hands. It will solve all your problems with docker and other issues also 😁.

[pkruithof]

Man I really feel for the contributors of this repo.

Please keep your OS flame wars out of this. If you don't want to use a Mac, try to change it at your company or otherwise find a new one. I can assure you that your ranting/trolling will do absolutely nothing to help your current issue.

[jrppl-dev]

Man I really feel for the contributors of this repo.

Please keep your OS flame wars out of this. If you don't want to use a Mac, try to change it at your company or otherwise find a new one. I can assure you that your ranting/trolling will do absolutely nothing to help your current issue.

Removed OS war from issue subject 🐧🐧

[claudinoac]

Having the same issue here with v4.7.0. The containers freezes up and then the daemon just stops responding.

Docker version 20.10.14, build a224086
Docker Compose version v2.4.1
Docker Desktop: 4.7.0
OS: MacOS Monterey 12.3.1
Processor: M1 Pro
Enabled Experimental Features

[os6sense]

I bought an M1 this week since a colleague was experiencing this issue. Seems to only happen whilst I'm doing a docker build of some frontend code. Pretty simple webpack build but running within tilt with lots of Elm and SaSS but somewhat surprising that this can kill the docker daemon.

One cause, which I just discovered, is that debugging the build in a running container with whatever the default memory limit is ending up hitting a lot of swap, dragging the build-time to minutes rather than seconds and sometimes crashing; adding an option to increase the hard memory limit (e.g. '--memory="2g"') solves this. I can run the container and do the webpack build, it takes seconds (amazingly fast actually, really shows what the m1 can do) and succeeds.

I'm still trying to work out how to apply this to docker build rather than a running container though; so far the command line options seems to ignore setting any memory limits and still crash the docker daemon.

Not a problem I normally have under ubuntu on AMD silicon, are the defaults different on the mac/m1? Is there anyway to change the defaults?

[tdxius]

Having the same issue with v4.7.0 on M1 chip when VirtioFS feature is enabled. The container becomes unresponsive and a restart is required.

[zenoleg]

Oh, I thought I am the only one having this bug. The same issue on Docker 4.6+
Downgraded to 4.5 to solve the problem.

MBP16 Intel
Docker version 20.10.12, build e91ed57
docker-compose version 1.29.2, build 5becea4c

[WayneYe]

Mac OSX 12.3.1
Docker Compose version v2.4.1

Ran into this issue since two weeks ago, frozen containers, couldn't stop contaienr, please fix it ASAP

[fredericdalleau]

Hey there, for those of you using the Experimental virtualization and virtiofs, macOS 12.4 beta 3 contains fixes for issues of containers freezing or VM crashing some time after enabling virtiofs. Let us know if you have any chance to try it!

In any case, could you upload diagnostic informations? You can refer to https://docs.docker.com/desktop/windows/troubleshoot/#diagnose-and-feedback
There is also the possibility to diagnostic from the command line if the UI fails to start.

[jrppl-dev]

I've confirme that disabling experimental features solve the issue.

With 4.8.1 with experimental features it was ok for several days. Our application was flying on mac os. Today suddendly reloading page frozes our container.

So I've updated to 4.8.2, which had the same issue. So in order to make sure I've deleted all images and build again, but without luck. After this I've disabled experimental features and all fine.

[jrppl-dev]

Good news

Issues with docker desktop on mac is really related to Mac OS version. I had the above issue with 4.8.2 and updated the mac os version. After that I've enabled experimental features and all working fine.

[WayneYe]

@jrppl-dev Glad to hear it works well for you after upgrading.

I've upgraded both Mac OSX and my Docker desktop to 4.8.2, so far I have seen some positive improvements

However, Pause/resume still didn't work.

[fredericdalleau]

@WayneYe try to see if a github ticket already exist on for-mac

[zenoleg]

Everything is good on Mac OS 12.4

[riki137]

Can confirm, Monterey 12.4 somehow fixed the issue, even with VirtioFS enabled.

[toniweser]

I'm on the latest MacOS Version (12.4, MacBook Pro 2021, Apple M1 Max) and on latest Docker Desktop Version (4.10.1). I tried several settings and combinations (experimental features like the new virtualization framework and the VirtioFs accelerated directory sharing), increasing or decreasing resources (CPUs, memory).

Unfortunately, sometimes docker containers are still freezing.

[pfk84]

Same here, 12.4, MacBook Pro M1 Pro, latest Docker Desktop version...

[jrppl-dev]

Hello everyone

Since updated to latest version, I never had similar issues.

Docker Desktop: 4,10,1

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked