-
Notifications
You must be signed in to change notification settings - Fork 372
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
Docker client code can no longer talk to the latest verson of the docker daemon 25.0.0 #2259
Comments
Added a PR to remove the version pinning as a first pass. Happy to change to pinning at a newer version if there is a good reason to do so. |
Thanks! Let’s discuss the details in #2260 . |
Would it be possible to cut a new release of c/image so that we can get an updated podman, buildah and skopeo out? |
@dcermak This is already included in a branched release of c/image, and e.g. in Podman 4.9.2, Buildah 1.33.5, Skopeo 1.14.2. Updating the mainline versions is, I think, currently WIP (around containers/buildah#5286 ), but it will certainly get done in the future. |
Miloslav Trmač ***@***.***> writes:
@dcermak This is already included in a branched release of c/image, and e.g. in Podman 4.9.2, Buildah 1.33.5, Skopeo 1.14.2.
Apologies, I missed that. Thank you for these releases!
|
The latest version of the Docker Daemon has now upped the minimum API version to 1.24 via this PR - moby/moby#46887
This now means tools such as skopeo fail against the 25.0.0 docker daemon with the following error
This is caused by the hardcoding of the API version to 1.22 here - https://github.com/containers/image/blob/main/docker/daemon/client.go#L14
This version on the containers/image side has not been updated for 7 years and it is now true that in the case a version is not set the client and daemon will try negotiate an API Version that they both support so that seems a cleaner solution but not sure if there is a good reason why a version would need to be set in this case.
The text was updated successfully, but these errors were encountered: