Updating to 4.41.2 has caused Docker Desktop launching to slow significantly. I want to revert to 4.41.1 to see if this clears the problem. I downloaded the appropriate installer, which is confirmed when it launches, and by examining the file properties. Unfortunately, the installer says Docker’s up to date, and ends. Running as a user, or as an admin - no difference.
I’ve done other updates (e.g., to 4.41.1) without a problem. This is the first time the wheels have come off.
Needless to say, I don’t want to completely scrub Docker and lose the five existing containers. Also, once launched Docker Desktop works as expected; it’s launching where the problem shows up.
---- The following excerpt from com.docker.backend.exe.log shows what I think is slowing startup:
[2025-05-15T05:29:56.992904100Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:30:01.829626000Z][com.docker.backend.exe.segment] flushing 166 messages
[2025-05-15T05:30:05.674057100Z][com.docker.backend.exe.marlin] sent message 200 OK (8682 ms)
[2025-05-15T05:30:05.680030300Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:30:06.831288800Z][com.docker.backend.exe.segment] flushing 49 messages
[2025-05-15T05:30:20.898150600Z][com.docker.backend.exe.marlin] sent message 200 OK (15221 ms)
[2025-05-15T05:30:20.902064700Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:30:21.829163000Z][com.docker.backend.exe.segment] flushing 51 messages
[2025-05-15T05:30:35.821045300Z][com.docker.backend.exe.marlin] sent message 200 OK (14922 ms)
[2025-05-15T05:30:35.828910300Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:30:36.831713800Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-15T05:30:51.258665000Z][com.docker.backend.exe.marlin] sent message 200 OK (15433 ms)
[2025-05-15T05:30:51.263562000Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:30:51.829403900Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-15T05:31:06.888667100Z][com.docker.backend.exe.marlin] sent message 200 OK (15629 ms)
[2025-05-15T05:31:06.894762200Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:31:11.829244900Z][com.docker.backend.exe.segment] flushing 49 messages
[2025-05-15T05:31:22.351136300Z][com.docker.backend.exe.marlin] sent message 200 OK (15459 ms)
[2025-05-15T05:31:22.352798800Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:31:26.831258600Z][com.docker.backend.exe.segment] flushing 51 messages
[2025-05-15T05:31:37.766974500Z][com.docker.backend.exe.marlin] sent message 200 OK (15414 ms)
[2025-05-15T05:31:37.773643400Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:31:41.829546200Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-15T05:31:53.085670800Z][com.docker.backend.exe.marlin] sent message 200 OK (15317 ms)
[2025-05-15T05:31:53.090934900Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:31:56.830693600Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-15T05:32:08.458432600Z][com.docker.backend.exe.marlin] sent message 200 OK (15372 ms)
[2025-05-15T05:32:08.468521300Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:32:11.829183000Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-15T05:32:23.628129300Z][com.docker.backend.exe.marlin] sent message 200 OK (15162 ms)
[2025-05-15T05:32:23.634135400Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:32:26.829697200Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-15T05:32:38.983031700Z][com.docker.backend.exe.marlin] sent message 200 OK (15355 ms)
[2025-05-15T05:32:38.993796800Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:32:41.831447200Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-15T05:32:54.328352700Z][com.docker.backend.exe.marlin] sent message 200 OK (15339 ms)
[2025-05-15T05:32:54.333677900Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:32:56.829422000Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-15T05:33:10.010020000Z][com.docker.backend.exe.marlin] sent message 200 OK (15679 ms)
[2025-05-15T05:33:10.018492100Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:33:11.829587800Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-15T05:33:25.400608900Z][com.docker.backend.exe.marlin] sent message 200 OK (15385 ms)
[2025-05-15T05:33:25.403107500Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:33:26.830337600Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-15T05:33:40.985861400Z][com.docker.backend.exe.marlin] sent message 200 OK (15584 ms)
[2025-05-15T05:33:40.993167000Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:33:41.829626900Z][com.docker.backend.exe.segment] flushing 49 messages
[2025-05-15T05:33:56.313645400Z][com.docker.backend.exe.marlin] sent message 200 OK (15328 ms)
[2025-05-15T05:33:56.318368700Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:33:56.830815400Z][com.docker.backend.exe.segment] flushing 51 messages
[2025-05-15T05:34:11.578497000Z][com.docker.backend.exe.marlin] sent message 200 OK (15263 ms)
[2025-05-15T05:34:11.586762100Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:34:11.831545200Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-15T05:34:26.665834500Z][com.docker.backend.exe.marlin] sent message 200 OK (15084 ms)
[2025-05-15T05:34:26.669781900Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:34:26.829237400Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-15T05:34:42.061671800Z][com.docker.backend.exe.marlin] sent message 200 OK (15393 ms)
[2025-05-15T05:34:42.069539500Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:34:46.838504800Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-15T05:34:57.491971000Z][com.docker.backend.exe.marlin] sent message 200 OK (15427 ms)
[2025-05-15T05:34:57.491971000Z][com.docker.backend.exe.marlin] sending 1 records
[2025-05-15T05:34:58.029362800Z][com.docker.backend.exe.marlin] sent message 200 OK (538 ms)
[2025-05-15T05:34:58.030038800Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:35:01.830590800Z][com.docker.backend.exe.segment] flushing 51 messages
[2025-05-15T05:35:13.561688700Z][com.docker.backend.exe.marlin] sent message 200 OK (15531 ms)
[2025-05-15T05:35:13.568394600Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:35:16.830360300Z][com.docker.backend.exe.segment] flushing 49 messages
[2025-05-15T05:35:29.006128100Z][com.docker.backend.exe.marlin] sent message 200 OK (15443 ms)
[2025-05-15T05:35:29.012549000Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:35:31.830136200Z][com.docker.backend.exe.segment] flushing 51 messages
[2025-05-15T05:35:44.378723800Z][com.docker.backend.exe.marlin] sent message 200 OK (15372 ms)
[2025-05-15T05:35:44.385824400Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:35:46.831063300Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-15T05:35:59.726326300Z][com.docker.backend.exe.marlin] sent message 200 OK (15348 ms)
[2025-05-15T05:35:59.730584400Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:36:01.829945300Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-15T05:36:14.808895000Z][com.docker.backend.exe.marlin] sent message 200 OK (15081 ms)
[2025-05-15T05:36:14.818528300Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:36:16.831200900Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-15T05:36:30.279572400Z][com.docker.backend.exe.marlin] sent message 200 OK (15467 ms)
[2025-05-15T05:36:30.285689700Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-15T05:36:31.829491300Z][com.docker.backend.exe.segment] flushing 50 messages
If you don’t have any data in containers, reinstalling it shouldn’t be a problem. Of course, even if the data is on volumes, deleting Docker Desktop would delete that too, but volumes could be saved before reinstalling. I would also use data bind mounted from a custom WSL2 disribution with WSL2 intergation enabled for persistent data instead of volumes, so I could completely delete everything any time and just run my compose files again in the WSL2 distribution to restore everything. I just leave it here for the future.
Back to the issue:
I don’t know what those logs mean exactly, except that I understand and see how long those took to finish.
Does it happen every time when you start Docker Desktop?
When it starts, what do you see on the GUI? Something like “Docker Engine is starting”? Or nothing? While it is trying to start, can you stop Docker Desktop or do you have to wait until it finally starts?
Regarding downgrade:
I’m not sure if it is a bug or feature. Instaling an older version should work. But My previous question could be relevant here too. If Docker Desktop could not stop completely, maybe it some processes are still running, and another version cannot be installed, although I would excpect a different error message then.
While DD is “spinning its wheels” (generating the messages I posted), there’s no sign of the GUI. It doesn’t show up for (loosely) several minutes after I launch it. Once it shows up, the process takes a reasonable amount of time to finish launching. FWIW, even older versions occasionally took more time (by a minute or two) than usual, ditto for shutting down. I take that to be “well, DD does that - get used to it.” [/smile]
I wanted to post more of the log, but being a “newb”, I was blocked with a warning about “too many links” - I assume that refers to URL’s in the log. If there’s a way to upload a full log as a file, I’ll be more than glad to do so - suggestions?
Just format the post the way I edited your first post and use code blocks like you would on GitHub, or in a MarkDown file so links and special charactrers will not be interpreted.
You can click on the pencil icon to see your first posts edit history and switch to the “RAW” tab.
Update:
I tried downgrading Docker Desktop. It worked on macOS but not on Windows. Then I started to remember an old discussion. I’m not 100% sure I remember correctly, especially since you mentioned it worked with older versions, but an upgrade can change things that can be harder to undo. For example some database file as Docker Desktop couldn’t handle every single version even those that didn’t exist when that version came out. So downgrade might not be possible unless Docker Desktop is uninstalled first. In that case you indeed need to backup all data and restore after installing the older version.
I could install an older version on macOS, but that is different as macOS works differently, so I can override the existing app just by copying the app over the old version. That doesn’t mean it would always work after downgrading, but I guess it is harder to detect a downgrade
Apologies for the slow reply - it’s been a busy day. I hate when reality intrudes…
I launched DD and the backendd.exe log shows about 7 minutes of “sent 50 records - flushing 50 messages - sent message 200 OK”
Once the GUI appears, everything works as expected, there are no messages with errors or warnings.
“It’s all good”.
I understand why reverting might cause more problems than it might fix. End of that.
Posting the full log fails (too long). Posting start to the 7 minute loop fails for the same reason. I hope this excerpt, with the loop, is useful.
2025-05-18T03:33:55.722237400Z][com.docker.backend.exe.updater] Checking module updates: []
[2025-05-18T03:33:55.722237400Z][com.docker.backend.exe.updater][W] failed to get module updates for DD 4.41.2: error while listing module updates: Get "http://ipc/modules/updates": open \\.\pipe\dockerModulesManagerAPI: The system cannot find the file specified.
[2025-05-18T03:33:55.722237400Z][com.docker.backend.exe.updater] new update state: no update found
[2025-05-18T03:33:55.722237400Z][com.docker.backend.exe.updater] checking for new update in background: no update found
[2025-05-18T03:33:55.756831800Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:34:00.575627300Z][com.docker.backend.exe.segment] flushing 160 messages
[2025-05-18T03:34:03.487043300Z][com.docker.backend.exe.marlin] sent message 200 OK (7731 ms)
[2025-05-18T03:34:03.495004500Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:34:05.577368200Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-18T03:34:18.267191700Z][com.docker.backend.exe.marlin] sent message 200 OK (14775 ms)
[2025-05-18T03:34:18.272681200Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:34:20.576085800Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-18T03:34:32.964518100Z][com.docker.backend.exe.marlin] sent message 200 OK (14692 ms)
[2025-05-18T03:34:32.971395300Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:34:35.575958600Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-18T03:34:48.257463700Z][com.docker.backend.exe.marlin] sent message 200 OK (15290 ms)
[2025-05-18T03:34:48.263500700Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:34:50.577443300Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-18T03:35:03.754434400Z][com.docker.backend.exe.marlin] sent message 200 OK (15493 ms)
[2025-05-18T03:35:03.762042900Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:35:05.578543500Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-18T03:35:19.047912800Z][com.docker.backend.exe.marlin] sent message 200 OK (15291 ms)
[2025-05-18T03:35:19.053888600Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:35:20.575538300Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-18T03:35:34.529046900Z][com.docker.backend.exe.marlin] sent message 200 OK (15480 ms)
[2025-05-18T03:35:34.538683700Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:35:35.576221400Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-18T03:35:50.155236100Z][com.docker.backend.exe.marlin] sent message 200 OK (15626 ms)
[2025-05-18T03:35:50.159914700Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:35:50.577908400Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-18T03:36:05.552500900Z][com.docker.backend.exe.marlin] sent message 200 OK (15397 ms)
[2025-05-18T03:36:05.558428900Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:36:05.575954300Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-18T03:36:21.101714800Z][com.docker.backend.exe.marlin] sent message 200 OK (15547 ms)
[2025-05-18T03:36:21.109806300Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:36:25.577027200Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-18T03:36:36.812356700Z][com.docker.backend.exe.marlin] sent message 200 OK (15707 ms)
[2025-05-18T03:36:36.817466000Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:36:40.576085000Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-18T03:36:52.369471200Z][com.docker.backend.exe.marlin] sent message 200 OK (15555 ms)
[2025-05-18T03:36:52.375186500Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:36:55.577183000Z][com.docker.backend.exe.segment] flushing 49 messages
[2025-05-18T03:37:07.922504100Z][com.docker.backend.exe.marlin] sent message 200 OK (15550 ms)
[2025-05-18T03:37:07.932497500Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:37:10.577212200Z][com.docker.backend.exe.segment] flushing 51 messages
[2025-05-18T03:37:23.538664800Z][com.docker.backend.exe.marlin] sent message 200 OK (15611 ms)
[2025-05-18T03:37:23.544269800Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:37:25.577147400Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-18T03:37:39.007556200Z][com.docker.backend.exe.marlin] sent message 200 OK (15468 ms)
[2025-05-18T03:37:39.014389600Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:37:40.576048900Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-18T03:37:54.277153500Z][com.docker.backend.exe.marlin] sent message 200 OK (15268 ms)
[2025-05-18T03:37:54.287146000Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:37:55.577406300Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-18T03:38:09.827590500Z][com.docker.backend.exe.marlin] sent message 200 OK (15545 ms)
[2025-05-18T03:38:09.837250700Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:38:10.576112200Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-18T03:38:25.247578100Z][com.docker.backend.exe.marlin] sent message 200 OK (15419 ms)
[2025-05-18T03:38:25.252289300Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:38:25.576010700Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-18T03:38:40.268349800Z][com.docker.backend.exe.marlin] sent message 200 OK (15019 ms)
[2025-05-18T03:38:40.277446700Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:38:40.576668900Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-18T03:38:55.690999000Z][com.docker.backend.exe.marlin] sent message 200 OK (15418 ms)
[2025-05-18T03:38:55.697130700Z][com.docker.backend.exe.marlin] sending 1 records
[2025-05-18T03:38:56.303426100Z][com.docker.backend.exe.marlin] sent message 200 OK (606 ms)
[2025-05-18T03:38:56.310198600Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:39:00.577385200Z][com.docker.backend.exe.segment] flushing 51 messages
[2025-05-18T03:39:11.778820600Z][com.docker.backend.exe.marlin] sent message 200 OK (15475 ms)
[2025-05-18T03:39:11.787920000Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:39:15.577088600Z][com.docker.backend.exe.segment] flushing 49 messages
[2025-05-18T03:39:26.770606000Z][com.docker.backend.exe.marlin] sent message 200 OK (14987 ms)
[2025-05-18T03:39:26.780918700Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:39:30.578897000Z][com.docker.backend.exe.segment] flushing 51 messages
[2025-05-18T03:39:42.438646700Z][com.docker.backend.exe.marlin] sent message 200 OK (15668 ms)
[2025-05-18T03:39:42.444994200Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:39:45.579898000Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-18T03:39:57.777278700Z][com.docker.backend.exe.marlin] sent message 200 OK (15336 ms)
[2025-05-18T03:39:57.783780800Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:40:00.576258900Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-18T03:40:13.468418500Z][com.docker.backend.exe.marlin] sent message 200 OK (15691 ms)
[2025-05-18T03:40:13.476237800Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:40:15.576386900Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-18T03:40:28.827677600Z][com.docker.backend.exe.marlin] sent message 200 OK (15359 ms)
[2025-05-18T03:40:28.830396300Z][com.docker.backend.exe.marlin] sending 50 records
[2025-05-18T03:40:30.576371000Z][com.docker.backend.exe.segment] flushing 50 messages
[2025-05-18T03:40:43.999323200Z][com.docker.backend.exe.marlin] sent message 200 OK (15172 ms)
[2025-05-18T03:40:43.999323200Z][com.docker.backend.exe.tracing] No OTLP endpoint defined, tracing will not be enabled
[2025-05-18T03:40:44.006567900Z][com.docker.backend.exe.features/unleash] fetching features from remote https://hub.docker.com/v2/feature-flags/proxy/
[2025-05-18T03:40:44.011255600Z][com.docker.backend.exe.clicontext] updated docker cli context desktop-linux
[2025-05-18T03:40:44.012420500Z][com.docker.backend.exe.clicontext] switching context from desktop-linux -> desktop-linux
[2025-05-18T03:40:44.014314000Z][com.docker.backend.exe.clicontext] switched to docker cli context desktop-linux
[2025-05-18T03:40:44.016772800Z][com.docker.backend.exe.socketforward] listening on virtual address: backend
[2025-05-18T03:40:44.016772800Z][com.docker.backend.exe.socketforward] listening on virtual address: 1999
[2025-05-18T03:40:44.023382000Z][com.docker.backend.exe.socketforward] listening on virtual address: http-proxy
[2025-05-18T03:40:44.023382000Z][com.docker.backend.exe.socketforward] listening on virtual address: http-proxy-restricted
[2025-05-18T03:40:44.023382000Z][com.docker.backend.exe.socketforward] listening on virtual address: 3128
[2025-05-18T03:40:44.023382000Z][com.docker.backend.exe.socketforward] listening on virtual address: hubproxy
[2025-05-18T03:40:44.023382000Z][com.docker.backend.exe.socketforward] listening on virtual address: 5555
[2025-05-18T03:40:44.023382000Z][com.docker.backend.exe.socketforward] listening on virtual address: dns.internal/grpc
[2025-05-18T03:40:44.023382000Z][com.docker.backend.exe.component] registering new settings subscriber: "*component.componentSettings[github.com/docker/pinata/common/cmd/com.docker.backend/internal/resyncer.settings]"
[2025-05-18T03:40:44.023382000Z][com.docker.backend.exe.component] registering new settings subscriber: "*component.componentSettings[github.com/docker/pinata/common/cmd/com.docker.backend/internal/resyncer.settings]"
[2025-05-18T03:40:44.023382000Z][com.docker.backend.exe.socketforward] listening on virtual address: dns.system/grpc
[2025-05-18T03:40:44.023382000Z][com.docker.backend.exe.socketforward] listening on virtual address: gvisor
[2025-05-18T03:40:44.025186900Z][com.docker.backend.exe.socketforward] listening on virtual address: vpnkit-data
[2025-05-18T03:40:44.040790600Z][com.docker.backend.exe.sys] Checking if a WSL update is required
[2025-05-18T03:40:44.041686200Z][com.docker.backend.exe.apiproxy] path controller settings changed: restarting approvers
[2025-05-18T03:40:44.041686200Z][com.docker.backend.exe.apiproxy] apiproxy settings changed: restarting API proxy
[2025-05-18T03:40:44.041686200Z][com.docker.backend.exe.apiproxy] closing proxies to trigger a restart
[2025-05-18T03:40:44.041686200Z][com.docker.backend.exe.apiproxy] closing
Given the problem started when the update to 4.41.2 dropped, I’m guessing something in the update isn’t as it should be. That would explain the “failed to get module” message. As to why the get failed… way, way past my pay grade.
If you’re patched to 4.41.2, please look for any of what I posted. I’m willing to put at least a virtual beer on your log not having either of these messages.
My main gig is as a fiction writer (Westerns, mostly). I have only very dated knowledge in the IT realm. So, I’ll live with the 7 minute delay, hope an update to 4.41.n (n>2) shows up, returning life to normal. If not, I might suck it up and build Docker again from scratch. Gngh…
My Windows got updates yesterday and I don’t get the messages with the “flushing messages”, but the Docker Engine cannot start and I can’t stop the GUI either. I reported it internally and I will share if I learn anything new.
It could be unrelated, but I rarely have issues with Windows recently and I can’t reproduces errors usually, so maybe there is something causing these issues with different error messages depending on the exact settings and environment.
update:
I restarted Windows and it showed that an update was on the way again. I could not see anything new in the update history, but Docker Desktop started. Not immediately, but after a couple of seconds and I still can’t see “sending 50 records” and similar status messages. It sends and flushes 1-3 messages once and not repeatedly.
For whatever reason the updates to Win 11 24H2 are currently failing. I’m not happy about the possibility the system’s somehow in trouble to the point updates fail. Given the current spate of problems with updates, maybe I’m not so upset over not getting the updates [\big grin]
As my favorite LLM says all too often, “that being said”, your report about DD leads me to think the 4.41.2 update didn’t go as planned, leading to the errors I’ve been getting. My hope is 4.41.n corrects the situation. I’d hoped reverting to 4.41.1 would also clear the problem, but, as you said, reversions may cause their own problems.
I’ll put up with the delay, and hope for an update soon. And hope it works better than the Win 11 24H2 updates.
