Docker is stuck at "Docker Desktop is stopping" after a minute of running containers #6549
Comments
|
same issue. M1 Pro. |
|
Probably a duplicate of this docker/for-win#13025, there have been a few related issues opened in the last few days. I faced the same thing on a Mac Mini M1, with Docker 4.13.0. I got it working again by reverting to 4.12. |
|
Got the similar issue, but its after a while of running containers, it stopped suddenly, tried "restart" in docker desktop also stuck, had to quit and start it again. |
|
I'm seeing this too - Diagnostics ID: 1B3E9A2C-D98D-4DE9-9235-43132318DE5C/20221027141440 Looking at the Console, each time my Docker instance stops it corresponds to a crash in com.docker.vpnkit. The last few crashes are all EXC_BAD_ACCESS, either SIGBUS or SIGSEGV. |
|
I am having this also. |
|
Issue might be related to vpnkit according to the crash log. I've tried downgrading to 4.12.0(85629) which seemed to solve the issue temporarily - been running 4.12.0 for 3-4 days without Docker Desktop crashing every half a day. |
|
Same downgrading to 4.12.0 has fixed the issue for me. |
|
I am having the same issue with OS 13.1 ... /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check [PASS] DD0027: is there available disk space on the host? [FAIL] DD0004: is the Docker engine running? Get "http://ipc/docker": EOF [PASS] DD0015: are the binary symlinks installed? |
|
Thanks for the report! ya, poking around in the diagnostics @atticusmatticus posted at the top of the thread, I do see vpnkit crashing a lot. We've gotten some reports of this, but aren't totally sure yet what causes it or why it only affects some users. Can you try upgrading to Docker Desktop 4.13.1 and see if that helps? (it has some recent vpnkit fixes) |
|
i think the issue @ackerthehacker2 is seeing is a very different issue, don't see any segfaults in your diagnostics, maybe file a new issue with repro steps and more details on what you're seeing? |
For me, 4.13.1 had the same crash in vpnkit. My containers have been running for 3 days now with no problems after downgrading to 4.12. |
|
On 4.13.1 on my Mac Mini M1 running Ventura it’s still happening. It seems related to containers opening too many connections at once. It would crash everytime I start downloads in Transmission. By reducing the number of allowed connections in Transmission (5 per torrent, 15 in total) it seems okay for now (no crash since this morning at least). Will report back if it happens again. Unfortunately I’m not at home now so I can’t really get logs. EDIT: Nevermind, it still crashes after a minute or two every time one of my running torrents gets active again. |
Have the same problem with 4.13.1; randomly crashes after a couple of days for me, this time it took about 3. The docker diagnostics currently show a pass on everything because I didn't think of running them before I killed the processes and restarted it. I've attached the macOS crash report: vpnkit_crash_report-06112022.txt |
|
Same for me as others, upgrading to 4.13.1 doesn't seem to change the issue appreciably. Still crashes after a minute or so once docker apps like Transmission start to make some connections and start transferring etc. |
|
Same happened in macOS 13.0 (22A380) when using docker desktop 4.13.1 (90346). |
is this consistent? crash every 3-4 days? mine just did after 3 days, def better than every 2-6hours. how are you monitoring the crashes? does it crash for the same reason every time? |
It's not really a timing issue. Mine has run just fine on 4.13.1 for a couple of days because I disabled Transmission. But I know if I enable it again, everything will crash as soon as my torrents get started again. |
|
Docker Desktop (Version 4.13.1 (90346)) also crashes on my (Intel x86-64 CPU) iMac. Console.app shows that com.docker.vpnkit crashes with EXC_BAD_ACCESS. Signal is sometimes SIGBUS; sometimes SIGSEGV. Two crash reports attached. No antivirus installed, but ElasticEndpoint/Elastic Security are installed. |
|
Same issues here. My entire team is having docker crash every 15-20 minutes. |
|
Thanks for the report. Does anyone have a self-contained repro I could try? (Edited to add: I've got some leads, based on the crash reports, but I want to make sure I'm looking in the right place.) Edit again: in case it helps, I've reverted some changes related to the stack traces. I have an Apple Silicon binary if you want to try it: To install it on Ventura I had to open up System Settings / Privacy & Security and add the Terminal as a program which can modify applications. This might be because of my local security settings though. The new vpnkit can be installed by: and then restart Docker. If this one still crashes (hopefully not), I'd be interested to see any new stack traces to see how they differ. |
|
I've installed your vpnkit version. It took 1-3 days for me to crash, so it might take some time until I can report back! :) Regarding the self-contained repo - in my case I'm just using the latest pi-hole image with no custom configuration or settings whatsoever.
|
|
Update: Docker Version 4.14.0 (91374) is crashing for me too in about 5 minutes of running 10 containers that are putting a lot of network traffic (network port scanning). The Dashboard shows the message: "Docker Desktop is stopped." I looked at the logs and found a segmentation fault in com.docker.vpnkit. I tried cleaning up the docker files, re-installing it, My system information: The actual com.docker.vpnkit carsh report is here: |
|
Just wanted to confirm this happens on my Mac M1 Pro with Docker Desktop v4.13.0, and seems to occur once a day apropos of nothing. No containers running and Docker Desktop is idle when it locks up. Crash log shows com.docker.vpnkit: |
|
Confirming this is happening on Docker Desktop v4.14.1 (91661), installed on Debian Linux. It generally will last an hour or so before entering this "Docker Desktop is stopping" state. Edit: Can also confirm that the problem no longer occurs after deleting Docker metadata and downgrading to 4.12.0 |
|
I am experiencing the same issue, vpnkit crashes pretty much 100% of the time when a container runs for few minutes. Basically same stack trace, it crashes in edit: Docker Desktop version is 4.14.1 (91661) and I'm running it on an M1 Mac |
Just reporting back, for me it hasn't crashed yet. |
I tried this binary today and it crashed on the second run of my container. The container generates 200-300 MB of network traffic in one run (based on the statistics in Docker Desktop). I checked before running that the vpnkit binary is correct: Here's the stack trace from the crashed thread: For reference, here's a stack from a crash few days ago: edit: the stack trace with slightly different offset from |
|
This issue is still present in docker v 4.15.0 |
|
I confirm v4.15.0 is still crashing for me. I'm staying at 4.12.0 for now. |
|
I have the same problem with docker 4.15 and macos 12.6 |
|
Me too. |
|
I'm testing the last 4.16.2 (95914) version (with macOs 12.6) and it doesn't 'stop' after minutes, it seems to work! :-) |
|
Have we found a solution to this? I am experiencing the same vpnkit crash with network traffic. As mentioned earlier, it always happens with torrents. Never with usenet downloads since it doesn't make many connections at once. the container will run indefinitely until there are torrent downloads, then I can almost never complete a torrent and often after the crash, I have to verify local data on torrents. I am running 4.16.2 (95914) |
|
I've been using 4.12 and it works great. I gave up on upgrading |
|
The remaining crash should be fixed in the upcoming 4.17. If you'd like to try a release candidate build: If there's still an issue, please upload some diagnostics, quote the ID here and I'll take a look. |
|
Facing the same problem as described here. Hiw can I reset docker? |
|
I think most of the issue (at least what I have run into) is based around the “in-place” upgrade.
If I do a uninstall and clean and “new install”. Things seem to work better.
rm -rf ~/Library/Group\ Containers/group.com.docker
rm -rf ~/Library/Containers/com.docker.docker
rm -rf ~/.docker
rm -rf ~/Library/Application\ Support/com.docker.docker
rm -rf ~/Library/Application\ Support/Docker\ Desktop
… On Mar 15, 2023, at 6:48 AM, Mike ***@***.***> wrote:
Facing the same problem as described here. Hiw can I reset docker?
—
Reply to this email directly, view it on GitHub <#6549 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJHJFL34CNOTKDJ5KNSFGG3W4GUCTANCNFSM6AAAAAARSKMIDY>.
You are receiving this because you were mentioned.
|
|
If someone has a better experience with 4.17 or another approach please let me know. I am using 4.12 and it works great. |
|
I'm using version 4.17.1 (windows), and I still have the same problem. [2023-03-29T00:03:24.943922100Z][com.docker.backend.exe][E] com.docker.vpnkit.exe with pid: 14560 shutdown with exit code 3221225477 |
|
Run the qbittorrent container and start 10 seeds. Waiting for a while, you will find com.docker.vpnkit.exe constantly collapse and restart. But as others say, the same container, V4.12 runs well. |
|
You can either downgrade to v4.12 or what just worked for me now was changing some of the following values in the docker settings.json file: Library/"Group Containers"/group.com.docker/settings.json to
|
|
I upgraded yesterday from 4.12 to Docker 4.19 on Mac OS latest and all my issues have been fixed. And the performance is improved significantly. |
|
I am facing a very similar issue here. Docker won't stop Postgres and desktop won't quit. 
It happens when I click the stop box/button. Running on version 4.33.0 (160616) macOS Monterey 12.7.6 I have to find all docker's PID and kill them or open Activity Monitor and kill everything also |
and others
Expected behavior
Before this started happening a day or so ago, I would start Docker Desktop and run
docker-compose up -dand my containers would start and remain on and operational for days.Actual behavior
Now, I run the same command with Docker Desktop running and within a minute or two Docker Desktop says "Docker Desktop is stopping" and never resolves from this issue. I have to force quit the application and all it's subprocesses to stop it and repeat trying to start it up. It always enters this endless loop of "stopping" within a couple minutes of running
docker-compose up -d.Information
Please, help us understand the problem. For instance:
Output of
/Applications/Docker.app/Contents/MacOS/com.docker.diagnose checkPrior to Docker Desktop getting frozen in this "stopping" state all diagnose checks pass. After the "stopping" message the checks are as follows:
Steps to reproduce the behavior
docker-compose up -dto start containersThe text was updated successfully, but these errors were encountered: