Error: request returned Internal Server Error for API route and version

Docker Desktop
,
1

Hi,

my docker “crashes” with the error: request returned Internal Server Error for API route and version ***** check if the server supports the requested API version

for all microservices im running in my docker-compose. This happens constantly, i might get my services up and running for a few min as longest. so i need to restart docker desktop alot.

Im running 2 docker-compose.yml files:
docker compose -f docker-compose.yml -f docker-compose.dev.yml up --build

the dev.yml file basically just override so it runs my services locally.

Mac OS: 14.4 (23E214)
Docker desktop: 4.28.0

Engine:
Version: 25.0.3
API version: 1.44 (minimum version 1.24)
Go version: go1.21.6
Git commit: f417435
Built: Tue Feb 6 21:14:22 2024
OS/Arch: linux/arm64
Experimental: false

1 Like
2

Hello, I’m seeing the same problem on my Windows 10 with Docker Desktop 4.28.

I just recently ran docker-compose up -d without a problem, but today it keeps failing with the same error you’ve mentioned.

3

Just hit the same issue.
Potentially the docker engine crashed.
Restarting fixed the problem for me.
as per Docker Error when Pulling Due to API Version - Stack Overflow

1 Like
4

Same issue on Windows today. Restarting the Docker engine worked for me.

1 Like
5

Restarting Docker Engine works for me

6

I restarted the docker engine and it worked one day after.

7

I am getting the same error

Error: “unable to get image ‘pgvector/pgvector:pg16’: request returned 502 Bad Gateway for API route and version http://%2F%2F.%2Fpipe%2FdockerDesktopLinuxEngine/v1.49/images/pgvector/pgvector:pg16/json, check if the server supports the requested API version”

I am running on windows 11 Docker desktop.
I tried restarting the docker engine many times and it till gives the error, before upgrade to v4.42.0 it was working fine.

Was trying to run the Nutrient AI Assistant docker image which requires pgvector database.

8

@narashimanatpspdfkit, Were you able to find a solution/workaround. I’m facing the exact same problem (with hashicorp/vault:latest) after upgrading to v4.42.0. :frowning:

9

Okay, I was finally able to resolve the problem.

For anyone facing this same problem, here’s what I did:

  • Uninstalled Docker Desktop.
  • Reinstalled Docker Desktop.
  • Re-setup the WSL integration (the checkboxes under General)
  • Updated docker-compose (from the Settings → Updates) page.

Lost all my volumes, but those didn’t have mission critical data, so I can live with it.

10

I had to remove all the existing images and containers, then restart Docker Desktop. After that, everything worked smoothly without any further issues.

1 Like
11

I wish you’d replied like 5 minutes ago… :sweat_smile:
But thank you. I’ll do that the next time I face this problem…

12

I was in a meeting. Immediately after my meeting I replied. Sorry for that.

13

Hey, no worries at all. I didn’t lose anything mission critical. :smiley:
Thank you… :upside_down_face:

1 Like