Skip to content
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

Support Docker API 1.45 #1420

Closed
scaddenp opened this issue Apr 23, 2024 · 7 comments
Closed

Support Docker API 1.45 #1420

scaddenp opened this issue Apr 23, 2024 · 7 comments
Milestone

Comments

@scaddenp
Copy link

Running selenoid/latest in portainer. Tests fail with this message:
Message: create container: Error response from daemon: {"message":"client version 1.12 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version"}

Docker API version on portainer is 1.45, Docker Compose version is v2.25.0

I dont get what that message is telling me.

@scaddenp
Copy link
Author

Selenoid has been working fine for ages. I believe the issue may have started with a Portainer upgrade to CE 2.19.4

@nhanvolac
Copy link

Same issue with me, after upgrading the Docker Engine to v26.1.0 (API version: 1.45) and running selenoid:1.11.2 -> can not create the container.

{"message":"client version 1.12 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version"}

@scaddenp
Copy link
Author

I notice a commit 3 months ago (Jan 25) meant address #1397 about the docker version. I am pulling /latest in the compose, but I am wondering if this has that fix.

@scaddenp
Copy link
Author

Looking at the startup log, I see:
"Did not manage to determine your Docker API version - using default version: 1.41"
@nhanvolac - do you see the same message?

@scaddenp
Copy link
Author

Changed compose to aerokube/selenoid:1.11.2 and get message:
Did not manage to determine your Docker API version - using default version: 1.44

But now I get no longer get the minimum API version error message. It now cant find the browser image which is a more reasonable message, as in processing off updating browsers

@scaddenp
Copy link
Author

Further. I updated Compose to specify the 1.11.2 image. And manually pushed a browser.json with updated chrome version, then downloaded the selenoid:chrome.123 version onto portainer. A run no longer produces that error message, and the chrome container is successfully started. Now getting message: "Could not instantiate class org.openqa.selenium.chrome.ChromeDriver" which might be config at my end or something missing with config (I cant execute CM).

@vania-pooh vania-pooh changed the title Not creating browser containers - client version is too old Support Docker API 1.45 Apr 30, 2024
@vania-pooh vania-pooh added this to the 1.11.3 milestone Apr 30, 2024
@alexander-tolstopyatov
Copy link

Same issue, I manually added environment variable DOCKER_API_VERSION with value "1.45" and error is gone. Looks like variable wasn't set somehow

vania-pooh added a commit to vania-pooh/selenoid that referenced this issue May 20, 2024
vania-pooh added a commit to vania-pooh/selenoid that referenced this issue May 20, 2024
vania-pooh added a commit to vania-pooh/cm that referenced this issue May 25, 2024
vania-pooh added a commit to aerokube/cm that referenced this issue May 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants