Sudden Docker error about "client API version"

Stewart

20 Jul 2023, 17:19 UTC

84.8K views1

I've been successfully using TestContainers with Docker for quite a while now. All of a sudden today, I started getting this error:

UnixSocketClientProviderStrategy: failed with exception BadRequestException (Status 400:
{"message":"client version 1.32 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version"}

What could explain such a sudden breakage?

1,716 following

1 answer

Accepted answer · original discussion

Jesse Glick

23 Jul 2023, 02:55 UTC

Permalink

There is an issue raised with Testcontainers about this.

If you can run Testcontainers 2.x, update to 2.0.2 or later. If not, update to 1.21.4.

If you cannot update at all for now, the following hotfix can be used as a workaround:

echo api.version=1.44 >> ~/.docker-java.properties

3 question comments

Use comments to ask for clarification. Post a solution as an answer.

AndyPermalink

21 Jul 2023, 22:07 UTC

There is already an issue reported directly on TC's GitHub - github.com/testcontainers/testcontainers-java/issues/11212, I suppose they will need to release a new version, given the Docker API version is almost (there is a workaround) hard coded in the library.

StewartPermalink

24 Jul 2023, 07:43 UTC

I have to say, I am amazed at the downvotes. To their contrary, I firmly believe this Q+A post is both clear and useful. People suddenly hitting upon this error will google the error text, find this post, and be able to immediately apply a fix and continue their work. Mission accomplished.

Keep exploring this topic

docker-desktop does not launch on ubuntu [Failed to start docker-desktop.service: Unit docker-desktop.service is masked]

I experienced this issue on Ubuntu 22.04 Jammy. After installing Docker Desktop, following the instructions on the official documentation , and meeting system requirements including having virtualization support, I am unable to launch the Docker Desktop GUI. I tried launching it from the applications menu but nothing. As an alternative to

Dependency issue installing google-chrome-stable through Ubuntu docker

I have a Dockerfile that attempts to install the package google-chrome-stable among other packages in Ubuntu (v16 Xenial I think) as part of a Gitlab pipeline step. I have had no issues until recently, when the step started failing with this issue: Some packages could not be installed. This may mean that you have requested an impossible s

Why I cannot run `apt update` inside a fresh ubuntu:22.04?

I currently don't manage to run apt update inside a fresh ubuntu:22.04 (codename jammy ). Protocol $ docker --version Docker version 20.10.2, build 2291f61 $ docker run --init --rm -it ubuntu:22.04 root@123456789:/# apt update Observed $ docker run --init --rm -it ubuntu:22.04 root@6444bf2cb8b4:/# apt update Get:1 http://archive.ubuntu.c

Docker: COPY failed: file not found in build context (Dockerfile)

I'd like to instruct Docker to COPY my certificates from the local /etc/ folder on my Ubuntu machine. I get the error: COPY failed: file not found in build context or excluded by .dockerignore: stat etc/.auth_keys/fullchain.pem: file does not exist I have not excluded in .dockerignore How can I do it? Dockerfile: FROM nginx:1.21.3-alpine

Sudden Docker error about "client API version"

1 answer

3 question comments

Your perspective belongs here.

Good answers start here.