You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 27, 2024. It is now read-only.
Not having to be on the bleeding age to use container-diff. Official docker-ce releases (stable and edge) are still on API v1.38. I suppose I could build from sources, but that's could be quite some effort only to discover that API 1.39 is actually required by container-diff. Is it?
Actual behavior
Container-diff fails because it is reporting API v1.39 to the server.
Information
container-diff version: Version 0.12.0 - 10/1/18
Operating system: debian stretch (amd64)
Steps to reproduce the behavior
# container-diff diff daemon://42bdaf9e6bc6 daemon://5772dc0624b7 --type=file
ERRO[0000] error retrieving image daemon://42bdaf9e6bc6: retrieving image from daemon: Error response from daemon: client version 1.39 is too new. Maximum supported API version is 1.38
error retrieving image daemon://5772dc0624b7: retrieving image from daemon: Error response from daemon: client version 1.39 is too new. Maximum supported API version is 1.38
The text was updated successfully, but these errors were encountered:
It looks like something in the negotiation is failing. For now you can override with DOCKER_API_VERSION=1.38 as an environment variable, but we should auto detect this better.
Expected behavior
Not having to be on the bleeding age to use container-diff. Official docker-ce releases (stable and edge) are still on API v1.38. I suppose I could build from sources, but that's could be quite some effort only to discover that API 1.39 is actually required by container-diff. Is it?
Actual behavior
Container-diff fails because it is reporting API v1.39 to the server.
Information
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: