Docker does not recover from resource saver mode #6933
Comments
ramki88
changed the title
|
Thanks @ramki88 we'll look in to this asap. Fyi, you can disable Resource Saver temporarily via Settings > Features in development > Experimental features. |
|
Hi @ramki88, sorry you hit a problem and thanks for filing the issue. Looking at the diagnostics bundle, I see Docker Desktop hit an internal error while entering resource saver mode: We will work internally to fix it. Out of curiosity, how often does this reproduce for you? Thanks! |
|
Hi @ctalledo, Thanks for you response. I have noticed these behaviour about 4 times today. Till now I have not observed any pattern. Will observe and report if I find anything. |
|
I have same problem. 
I tried Factory Reset, but it doesn't changed. |
|
I am having similar issues with the I have restarted my laptop, once I then start Docker Desktop it starts back in Saver mode but I am unable to do anything. I can't run docker build, restarting and clean/purge data don't respond with anything and |
|
Have the same issue with version 4.22.0 (117440)
Please provide a work around, a config option to deactivate this or make sure, it wakes up correctly when used. |
|
Hi - I installed 4.22.0 last week and it was working on Friday 8/4. Today i have the same issues as the others. |
|
Hi folks, Cesar Talledo from Docker here. Sorry to hear you are having trouble with the resource-saver feature, and thank you very much for reporting the problem. First, quick context: The resource saver feature is meant to significantly reduce Docker Desktop's memory and CPU usage on the host when no containers are running, to improve overall user experience. It will reduce mem utilization by ~2GBs (or more) when DD goes idle. In DD v4.21, the feature would simply pause processes in the DD Linux VM, but in v4.22 we improved it to shutdown the DD Linux VM. We did a lot of testing prior to releasing the feature and for most users it's working well, but a few are reporting problems. Our apologies, we will try to fix them ASAP. For those of you experiencing problems:
The file can be found here: Mac: After you disable the feature, make sure to quit Docker Desktop and start it again via the Whalemenu on the taskbar (don't just simply click "restart" on the Whalemenu). If you have any issues with this, please let us know. Thanks again and we hope to fix all issues very soon. |
|
We are investigating the issue internally. To help us reproducing the issue could you upload a diagnostics bundle and share the id? @bconfrancisco @hrabe @mikelax @kangaechu . Thanks in advance! |
I have the same problem. My diagnastic id is: 17381DA9-8BEE-4201-8FF2-0FB58278F01C/20230808113242 |
@bsousaa Here is an ID: D037C0D1-560C-409B-A11C-0629819A44CE/20230808114543 One item of note, I first started Docker this morning and immediately ran the Diagnostics and uploaded. During this time Docker appeared to be in regular mode. As soon as the Diagnostics ID uploaded completed then Docker switched into "Resource saver mode". |
|
Diagnostic ID: 8C632EC5-F963-42AB-B88E-4342E129FF2F/20230808115322 I keep getting this error Docker is in resource saver mode |
|
Diagnostic ID: 8E671B87-5DFC-45A8-8460-34DBFE462181/20230808152154 MacOS Monterey: Version 12.5.1 |
|
I've also been having this issue with version I can't quit/start/restart docker via the Whalemenu on the taskbar. Quitting Docker Desktop via the app makes the app/UI disappear but the taskbar Whalemenu doesn't change and shows it's still running. I'm new to Docker though so this could be the expected behavior. Diagnostic ID: 480CE2DB-48A1-4BB8-8B7B-78C895F45DAD/20230808163825 @ctalledo I don't seem to have |
|
Hi @safayildirim, apologies you hit this issue (we are on it) and thanks for uploading the diagnostics bundle, very helpful.
Yes, that's what you should do: create a new |
|
Thank you @bconfrancisco @benjaminreji @mikelax @safayildirim @safayildirim for uploading the diagnostics bundle, this helps us root cause the problem. |
|
Diagnostic ID: 60C25128-558D-4678-9961-8E6CA9B9DE27/20230809012117 |
Thanks @kangaechu; I looked at the diagnostic bundle but did not see any failure with the resource saver feature. Did it fail for you somehow? Or are you just looking to disable it? Thanks. |
|
@ctalledo |
|
Same issue for me in 4.22 on macOS Ventura 13.4.1. Containers were stopped the Mac was put on sleep. When waking up the docker is in Resource Saver mode and unresponsive. Diagnostic ID: 0408424A-469D-48B6-8B3F-B92D0868B079/20230810045901 |
|
+1 same issue for me in v4.22.0 on macOS Ventura 13.4.1. |
|
Hi @ctalledo Did install 4.24.3 (125250) till now unable to reproduce the issue. The last time it happened was when devcontainer was started from vscode while the docker was in resource saver mode. But today tried it multiple times and DD recovered as expected. Will update if the issue reoccurs. Thanks! |
|
@ctalledo Unfortunately, 4.24.3 still exhibits the failure to wake from Resource Savor mode for me.
|
|
Same issue, I had to disable resource saver |
|
Same issue. I'll disable the resource saver... running on Windows 11 with Desktop 4.24.2 (124339) |
|
Hi Chip (@lgw4), thanks again for trying with the custom build I provided and reporting the failure. I am still trying to figure out why Docker Desktop sometimes fails to power up the Linux VM on your host, and to be honest I don't yet have a strong clue. On my Mac host (Mac Air with Apple M2 chip + Ventura), I can have DD enter/exit resource saver mode hundreds of times without problem. So it's something subtle. One thing I noticed, is that in your host, Docker Desktop is filesharing the I am wondering if disabling that makes a difference; if possible could you try removing the Thanks again for all the help, we appreciate it. |
|
I also had to disable resource saver. Its pretty amazing that this functionality made it to a public release. It basically bricks my Docker desktop instance on MacOS (ARM) |
Thanks @cosmotek for reporting; if possible please collect and upload a diagnostics bundle so we can take a look.
Quality is very important to us, and this feature was tested thoroughly before release. In fact, out of almost 1M users using the resource-saver feature, less than 1% are currently hitting errors. Nonetheless we understand your frustration (as well as that of other users experiencing problems), and therefore continue to work diligently to debug all issues. But it's not easy, especially since we can't always reproduce the problem locally due to the large variety of machine setups across our users. We appreciate you reporting the issue though, and ask for patience as we debug all the problems with the feature. Thanks! |
|
Hi @umayrh,
Thanks for reporting; in your case I see the following error when Docker Desktop exits resource saver mode (i.e., when it tries to power up the Linux VM to run the Docker Engine inside): That's an error coming from the MacOS hypervisor; unfortunately there's no information on what caused that VM crash, but having low memory (RAM) on the host could be one reason. Not sure if that's the case in your scenario, because the diagnostics bundle was captured after the fact. If you hit this again, please check the RAM utilization on your host at the time. Otherwise you may want to disable the resource saver feature to prevent this from re-ocurring. Thanks! |
|
Hi @frobinette, Thanks for reporting.
Did you mean DD goes into resource saver mode and doesn't come out? Or that it never went into resource saver mode when it should have? I looked at the diagnostics bundle you collected (thanks for that), but did not spot any issues with resource saver. I can see DD went into resource saver mode 23 times, and in all of them it came out fine. Let me know if I am missing something; thanks! |
Hi @ctalledo! Thanks for looking at this. What I mean is DD is going out of resource saver mode when I think it should not. I'm not starting any container nor running docker commands. And like you said it stays out of resource saver mode without re-entering it after 30 secs... Is there any watchdog/checks that can cause DD to go out resource saver mode automatically and preventing it to go back in resource saver mode again after 30 secs? Again, thanks for looking at this! |
|
Hi @frobinette,
Oh got it, thanks for clarifying. Yes, there are some internal watchdog checks that can cause DD to go out of resource saver mode periodically, though it should always go back into resource saver mode. We are working to improve that, so that once it enters resource saver mode it stays there until user-driven activity requires DD to start the VM. Try also with the latest DD (v4.25) because there have been improvements in this area. Thanks again! |
|
Hi @aevenstad,
Thanks for reporting and uploading the diagnostics; that helped us catch a bug during resource saver exit which we've just fixed. The bug you hit is different than most other users in these issue have hit. The fix will be present in v4.26. Thanks again! |
|
This is happening on my Mac Pro, here's the diagnostic id: D4A82B8F-DBC5-4E65-A8C9-7830F4AAF5D8/20231027141308 |
|
It's also happening on my Mac Studio Apple M2 Max 32 GB - Sonoma 14.0 Report (click here)------------------------------------- Translated Report (Full Report Below) -------------------------------------Process: Docker Desktop [14479] Date/Time: 2023-10-28 22:17:51.5014 -0300 Sleep/Wake UUID: CE6D1C12-23F2-4575-9DB7-41FB12669B0D Time Awake Since Boot: 700000 seconds System Integrity Protection: enabled Crashed Thread: 11 Exception Type: EXC_CRASH (SIGABRT) Application Specific Information: Thread 0:: CrBrowserMain Dispatch queue: com.apple.main-thread Thread 1: Thread 2:: ThreadPoolServiceThread Thread 3:: ThreadPoolForegroundWorker Thread 4:: ThreadPoolBackgroundWorker Thread 5:: ThreadPoolForegroundWorker Thread 6:: Chrome_IOThread Thread 7:: MemoryInfra Thread 8: Thread 9: Thread 10: Thread 11 Crashed: Thread 12: Thread 13: Thread 14: Thread 15: Thread 16: Thread 17: Thread 18:: NetworkConfigWatcher Thread 19:: CrShutdownDetector Thread 20:: NetworkConfigWatcher Thread 21:: ThreadPoolForegroundWorker Thread 22:: ThreadPoolSingleThreadForegroundBlocking0 Thread 23:: CompositorTileWorker1 Thread 24:: ThreadPoolSingleThreadSharedForeground1 Thread 25: Thread 26:: com.apple.NSEventThread Thread 27:: NetworkNotificationThreadMac Thread 28:: ThreadPoolForegroundWorker Thread 29:: NetworkConfigWatcher Thread 30:: ThreadPoolBackgroundWorker Thread 31:: ThreadPoolForegroundWorker Thread 32:: ThreadPoolSingleThreadSharedForegroundBlocking2 Thread 33:: CacheThread_BlockFile Thread 34:: ThreadPoolSingleThreadSharedBackgroundBlocking3 Thread 11 crashed with ARM Thread State (64-bit): Binary Images: External Modification Summary: Full Report{"app_name":"Docker Desktop","timestamp":"2023-10-28 22:17:52.00 -0300","app_version":"4.24.0","slice_uuid":"4c4c44ab-5555-3144-a150-ea82ea2f4222","build_version":"4.24.0.10","platform":1,"bundleID":"com.electron.dockerdesktop","share_with_app_devs":0,"is_first_party":0,"bug_type":"309","os_version":"macOS 14.0 (23A344)","roots_installed":0,"name":"Docker Desktop","incident_id":"BA73034E-EFF4-4DD7-90C6-86A2890799CE"} } ], Model: Mac14,13, BootROM 10151.1.1, proc 12:8:4 processors, 32 GB, SMC |
Hi @ctalledo , I can confirm my issue is gone with version 4.25. It enters and leaves Resource Saver mode without problem. Thanks! |
|
@jwcunhagit can you please put your long output in <details>
<summary>Report (click here)</summary>
(your report output here)
...
...
</details>will look like this: Report (click here)(your report output here)... ... |
@ansiwen done, thank you. |
|
Updated to Docker Desktop 4.25.0 (126437) and it appears as the issue has been fixed. DD returns from resource saver to normal operation instead of freezing. 2023 MBP M2 Pro, Sonoma 14.1 |
|
Getting this error and couldnt fix it with the help of this thread. @ctalledo |
|
Hi @spointecker, thanks for filing the report. In your case it seems the issue is not a resource-saver bug per-se, but rather the Docker Engine failing to boot (probably while exiting resource saver mode) due to lack of space inside the Docker Desktop VM: Please try increasing the VM's disk size in the Docker Desktop settings -> Resources window and restart Docker Desktop. Additionally, once Docker Desktop is up and running, consider removing old/stale images that may be taking up too much space. Nonetheless, I acknowledge we need to improve Docker Desktop's error handling in this case so as to provide a clear error when such problems occur. I'll take that as an action item. |
Hi @ctalledo, EDIT: |
|
Hi @spointecker,
I see; please try updating the settings directly via the Docker Desktop settings file then: Mac: The setting you are looking for is Hope that helps! |
Thank you very much, that worked like a charm! |
|
Docker v4.25.2 still same issue in macos sonoma. Once resource saver is active both docker desktop and docker commands become unusable. Only way to quit is to use activity monitor and force quit all docker executables and then restart. (docker-compose up commands in cli just hang/wait without output. selecting quit, or restart in the docker desktop from menu or dashboard is not responding). The docker desktop gui also does not allow disabling resource saver anymore. |
|
@w-A-L-L-e can you please share a diagnostics id? |
This setting is not available at the location specified in Docker Desktop v4.26.1. Followed Aug 7 advice from @ctalledo and the issue was resolved. Oddly the configuration file disappeared after restarting the docker daemon from the Whalemenu. |
and others
Description
After the recent update, docker does not seem to recover from resource saver mode. In the dashboard CPU and Mem shows zero and all docker commands do not respond or wake the engine. Only after a restart of the engine it starts to respond
Reproduce
docker info
Expected behavior
"
docker infoshould provide the info about dockerdocker version
Client: Cloud integration: v1.0.35-desktop+001 Version: 24.0.5 API version: 1.43 Go version: go1.20.6 Git commit: ced0996 Built: Fri Jul 21 20:32:30 2023 OS/Arch: darwin/arm64 Context: desktop-linux Server: Docker Desktop 4.22.0 (117440) Engine: Version: 24.0.5 API version: 1.43 (minimum version 1.12) Go version: go1.20.6 Git commit: a61e2b4 Built: Fri Jul 21 20:35:38 2023 OS/Arch: linux/arm64 Experimental: true containerd: Version: 1.6.21 GitCommit: 3dce8eb055cbb6872793272b4f20ed16117344f8 runc: Version: 1.1.7 GitCommit: v1.1.7-0-g860f061 docker-init: Version: 0.19.0 GitCommit: de40ad0docker info
Diagnostics ID
073CCF80-81D3-426A-A5F1-1B13A4481DE2/20230804091953
Additional Info
No response
The text was updated successfully, but these errors were encountered: