Docker http://containers/json endpoint depreciation notification #900
Labels
Comments
|
As far as I could find, the docker client always uses an explicit version number ("v1.18" and "v1.24"). Going back through the code, it seems like it has always been the case. |
gnosek
added a commit
that referenced
this issue
Dec 6, 2017
gnosek
added a commit
that referenced
this issue
Dec 6, 2017
As of this writing, Docker recommends at least v1.24, so we use that. However, for e.g. RHEL 6/CentOS 6, which are stuck on Docker 1.7 with API version 1.19, we do a fallback request without the version number. This way, we use v1.24 if possible, and the newest supported version if not. Closes: #900
gnosek
added a commit
that referenced
this issue
Dec 6, 2017
As of this writing, Docker recommends at least v1.24, so we use that. However, for e.g. RHEL 6/CentOS 6, which are stuck on Docker 1.7 with API version 1.19, we do a fallback request without the version number. This way, we use v1.24 if possible, and the newest supported version if not. Closes: #900
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is more of a general informative post following up a conversation in #falco with @mstemm.
Docker has depreciated the
http://containers/jsonendpoint and all future API calls should be prepend the API version. e.g.http://v1.25/containers/json.It is targeted for removal in the v17.12 release.
For further information, please see the below links:
The text was updated successfully, but these errors were encountered: