New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Latest release 4.22.0 very unstable - docker desktop mac #6953
Comments
I'm experiencing the same. After I updated and installed nothing else, |
We released the 4.22.1 patch fixing multiple issues https://docs.docker.com/desktop/release-notes/. Can you give it a try? |
I am experiencing the same problem(s) described by @brokengrappler and @paro-paro on 4.22.1. My system:
EDIT: I was wrong - I ended up downgrading to 4.21.1, which works perfectly |
F14EC0BF-E65E-45F4-B960-78F5BD1C8BD8/20230828180056 |
@daveisfera can you confirm what version of Docker Desktop you are running and describe the issue? |
4.22.0 and everything froze up. Even |
I am running 4.22.0 on a mac. It seems flaky. For instance, running a tutorial, sometimes |
@stevehs17 please upgrade to 4.22.1. @daveisfera can you confirm if the issues are gone? |
The issue is infrequent and random, and I've only been running for about a day, so can't say anything sure yet, but I'll keep an eye out |
@bsousaa I had similar problems yesterday with 4.22.1. I'll try it again today. If I keep having problems, I'll try 4.21.1 and see if that works better. |
I upgraded to 4.22.1 (Windows) and it is very unstable - at least as unstable as it was 4.22.0 (running it on Windows) |
After having problems with both 4.22.0 and 4.22.1 on Mac, I decided to try 4.21.1 based on comments previously in this thread. It seems to work much better. One clear advantage is that it starts much more quickly. |
I went back to 4.21.0 as well. All is running fine, as it did before, without issues. |
I rolled back to 4.21.1. works like a champ! |
docker crashed in a way I haven't see before:
F14EC0BF-E65E-45F4-B960-78F5BD1C8BD8/20230831205555 |
I don't have a specific log, however I just wanted to add similar confirmation like Steve's.
Same, and my problems were things like not being able to use docker-ps/cli etc, and my tools that work with docker couldn't detect the instance despite Desktop running, and restarting Docker Desktop in-app didn't make them work either. Only a full system reboot got it to work for a bit before it went weird again eventually. My only guess at the moment is perhaps it's that new power saving mode? But that's a wild guess on my end. In any case 4.21.1 works fine for me. On an M1 Mac running Monterey. |
F14EC0BF-E65E-45F4-B960-78F5BD1C8BD8/20230920193202 |
Seeing something similar - docker-build not longer works on mac, getting identical error |
ERROR: request returned Internal Server Error for API route ... |
@manvydas-tbol @apanasenkamaksim can you share a diagnostics id? https://docs.docker.com/desktop/troubleshoot/overview/ |
@bsousaa Error uploading: Put "https://docker-pinata-support.s3.amazonaws.com/incoming/3/649EA5DE-AE01-4F94-8CA2-DD3BF2EAEA0E/20230922172459.zip": write unix ->/Users/myusername/Library/Containers/com.docker.docker/Data/httpproxy.sock: write: no buffer space available Maybe this is the issues itself. |
Maybe, not. |
Froze up again and all 8 cores going full bore in the virtualization stuff: |
Hello, This issue has been fixed in the latest 4.24.0 release. You can see the latest release notes here. Would you mind trying it out and checking if the issue still persists? |
Hi, Thank you! |
Description
Just updated to the latest 4.22.0 version.
Half of my images wont run. Like this one:
Both the cli and the UI have frozen many times trying to run and remove both containers and images.
Even after a full cleanup with
docker system prune
the UI will still display unused images.Just wanted to report this here in case other users are having the same issues.
Uninstalling and going back to previous version (4.21.1) fixed all issues.
Reproduce
Explained above
Expected behavior
No response
docker version
docker info
Diagnostics ID
Additional Info
No response
The text was updated successfully, but these errors were encountered: