-
Notifications
You must be signed in to change notification settings - Fork 118
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
request returned Internal Server Error for API route and version 4.22.1 #6956
Comments
I'm seeing this regularly in DDEV automated tests. This is now DD 4.23.0 Diagnostic: CE46F4CE-5EA3-46A1-BB0A-7FF47A7B2E10/20230923002402
|
Another diagnostic, on another machine: 358979A2-0D9F-4631-894B-EA8807C2A1EE/20230923193151 @engFelipeMonteiro could you please update the title to include something of the error message? The title could be "request returned Internal Server Error for API route and version", people might find it faster. |
This is happening on Windows also, same thing: |
Another one here.
Finally,
|
Me too. The message:
|
hello ,have you solved this problem? |
hello ,have you solved this problem? |
Likewise, same problem
|
I am now able to successfully create/run containers on my M2 Mac. In Docker Desktop, hit settings, go to "Features in Development", and turn ON "Use Rosetta". |
@aboggis-lc if you are on Apple Silicon and need Rosetta to run arm64 containers (for example, |
Perhaps. I am just reporting what resolved my issue, which, at the time, seemed related. Hence my previous post. |
so what's the solution> |
Upgrading to docker desktop version 4.24.2 (124339) has resolved the issue for a colleague of mine. |
This worked for me! |
nasty solution, but worked for me
3- |
I had the same problem. I stopped Docker and ran it with Administrator privileges. If you have a shortcut, change it to run Docker with Administrator privileges, and the issue should be resolved. |
Thank you, my problem has been solved. I upgraded docker to the latest version.
…------------------ 原始邮件 ------------------
发件人: ***@***.***>;
发送时间: 2023年10月28日(星期六) 中午12:05
收件人: ***@***.***>;
抄送: ***@***.***>; ***@***.***>;
主题: Re: [docker/for-mac] request returned Internal Server Error for API route and version 4.22.1 (Issue #6956)
我也有同样的问题。我阻止了Doker并以管理员权限启动了它如果有快捷方式,将其更改为具有管理员权限的Docker,问题将得到解决
—
Reply to this email directly,view it on GitHub,orunsubscribe.
You are receiving this because you commented.Message ***@***.***和>
|
Thanks very much. Your solution worked for me |
I am running 4.25.0 and its still happening, Docker appears to run for a short period of time (~10 mins) before freezing and returning the Internal Server Error when running "docker ps" |
It ran for couple hours today (although previous run was like 10mins) - Can someone direct me on how I can assist on this, provide logs etc ? This is terribly frustrating as it occurs several times a day. |
I am currently trialing running as Administrator
|
You won't regret it. Was life changing for me. Went from needing to restart Docker 1-2 times per day to never even needing to think about it. Months of it working flawlessly. Set up was a breeze, interface is minimalistic. |
@austinarchibald agreed - already been running for 7 hours without incident after crashing every 20 minutes. Simple migration. Hope the docker team considers addressing these issues at some point. |
I have the same issue since about 3 weeks ago (?), docker became pretty unusable due to this. I have to factory reset every day, sometimes its working for somehours, sometimes i have to reset it within 10 minutes again. I also have the feeling that this is related to network problems, or long internet latency or wifi switching.. Can't tell exactly, but it happens quite often when the network is or was down / wifi switching, registry was slow or internet was slow.. |
Same problem here, docker is not stable in the last month |
$ docker image prune -a -f --filter until=240h
request returned Internal Server Error for API route and version http://%2FUsers%2Fnikbr%2F.docker%2Frun%2Fdocker.sock/_ping, check if the server supports the requested API version Still happens with 4.29 |
For me worked this experimental build which enables a TCP kernel network flag: #7240 (comment) |
Can confirm this also worked for me. |
Yeah likewise it worked for me |
khwilo's answer worked for me, thanks 🙏 |
Having same issues on docker desktop 4.30.0 with M3 on a large docker compose. Use Rosetta is enabled |
@laygir you should try OrbStack, it is a 100% drop in replacement. Download it, install it, Quit Docker Desktop, do your stuff, it works without any changes - I love it. |
@stevef51 What about a local Kubernetes cluster. Does it set all that up for you as well? |
@jkugler I have some experience with k8s, but not recently. I see OrbStack supports k8s in the docs, but I have not used it - if its anything like the Docker support then it should be good. The beauty of OrbStack is it just works, I tried Podman as a replacement a while back and it kinda worked after some config changes, but I could not get it to work with VSCode Dev Containers which is a must for us - OrbStack worked without changing anything - give it a try, if it doesnt work you just uninstall it and restart Docker and your back to where you are now |
Macbook Pro M2 with Docker desktop v 4.30.0 and I still see this error after re-building container. weird. |
I had the same error with MacBook Pro M1 Pro, what the error might be suggesting is that the docker daemon just died. Restarting docker-desktop for me fixed the issue. |
Same on M1 Pro with v4.31.0. Restart helps for a little while and then crashes again |
The same configuration. Just changed some settings (with restart) and it helped, but after 5 minutes (while writing this comment) bug has appeared again. Upd. |
I've to restart a couple of times to can use Docker. I'm using MacOs 14.5. But this happens with some images. I don't understand what is going on.... Someone knows? |
The same for me. Docker engine v4.25.2 |
Same issue for me, mac m1 , had to restart docker desktop and it finally went back to normal |
Also an issue for me since latest docker desktop update on mac m1. Happens really often |
Same as well. Happens every hour or so. |
This keeps happening; happens when your internet is not working great and you might experience micro cuts. 🙄 |
Since I found OrbStack I have not looked back - dont get me wrong, I love
Docker and what they have done for containerisation but this issue was a
big one and I can't believe its still occurring 6 months after I initially
experienced it. OrbStack is Mac specific, faster and provides more
features than Docker for Mac/Windows.
…On Fri, Aug 2, 2024 at 12:12 AM Yael Brodsky ***@***.***> wrote:
This keeps happening; happens when your internet is not working great and
you might experience micro cuts. 🙄
—
Reply to this email directly, view it on GitHub
<#6956 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHJOXM6CKOUADSXAFS4RKLZPI66VAVCNFSM6AAAAAA4AAZHOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRTGE4DMNRSGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Yes, Orbstack immediately solved all my problems with docker on mac. It has been so solid, have not experienced a single crash in the past 7 months since switching. Whereas I was getting almost daily crashes on docker desktop. |
The problem I had with Orbstack is that when it imports from docker it does not import the networks. So when trying to fire up the containers it imported they crashed because of missing network. Got stucked there, had to limp back to docker. |
@ybrodsky this is no different to setting your system up on a new Docker system, you would have to create those networks which are easily done using the exact same syntax docker network create mynetwork The beauty of OrbStack is that I have found it to be a 100% drop in replacement. I did not use the OrbStack import Docker data, I just re-ran all my Docker setup scripts (to create volumes, networks) and rebuilt images - but I did not have to change a single line of code, it rebuilt and runs perfectly. |
Description
I installed the latest version of docker-desktop, and couldn't make the docker-cli connect to docker-server.
Hardware: MacBook Pro M2 8GB
OS: MacOS Ventura 13.4.1 (c)
Docker: Docker Desktop 4.22.1 (118664)
Diagnostics ID: B51D4228-3485-49B7-B20D-AFDCA2E977C7/20230827032005
Reproduce
% docker info
Client:
Version: 24.0.5
Context: desktop-linux
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.11.2-desktop.1
Path: /Users/felipemonteirojacome/.docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.20.2-desktop.1
Path: /Users/felipemonteirojacome/.docker/cli-plugins/docker-compose
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.0
Path: /Users/felipemonteirojacome/.docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.20
Path: /Users/felipemonteirojacome/.docker/cli-plugins/docker-extension
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v0.1.0-beta.6
Path: /Users/felipemonteirojacome/.docker/cli-plugins/docker-init
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: /Users/felipemonteirojacome/.docker/cli-plugins/docker-sbom
scan: Docker Scan (Docker Inc.)
Version: v0.26.0
Path: /Users/felipemonteirojacome/.docker/cli-plugins/docker-scan
scout: Command line tool for Docker Scout (Docker Inc.)
Version: 0.20.0
Path: /Users/felipemonteirojacome/.docker/cli-plugins/docker-scout
Server:
ERROR: request returned Bad Gateway for API route and version http://%2FUsers%2Ffelipemonteirojacome%2F.docker%2Frun%2Fdocker.sock/v1.24/info, check if the server supports the requested API version
errors pretty printing info
Expected behavior
No response
docker version
Cannot connect to the Docker daemon at unix:///Users/felipemonteirojacome/.docker/run/docker.sock. Is the docker daemon running? 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
docker info
Diagnostics ID
B51D4228-3485-49B7-B20D-AFDCA2E977C7/20230827032005
Additional Info
No response
The text was updated successfully, but these errors were encountered: