Smarter API version handling
See original GitHub issueDescription
As described in https://github.com/fabric8io/fabric8-maven-plugin/issues/1200 the minimal version 1.18 used by d-m-p gets rejected for newer Docker daemons (e.g. those having 1.35).
Actually we are compliant with the newer versions (its a minimal version after all), so I see two solutions:
-
If possible, we don’t send an API version. However when we use features which require a minimal version of 1.21 this still will still break.
-
We send a test request to the Daemon, and check whether it succeeds. In the return response there’s a header
Api-Version:
which holds the actual Docker daemon version. So if this test request because of a too low version, we can just pick up that version and use it as minimal version for us.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6
Top Results From Across the Web
API Versioning: A Marketer's Guide - HubSpot Blog
API versioning is the practice of managing changes to an API and ensuring that these changes are made without disrupting clients. A good...
Read more >Handling API versioning - Cloud Endpoints
This page describes how to do versioning for your API and how to deploy to multiple versions. Recommendations for managing API versions. In...
Read more >Everything You Need to Know About API Versioning
A proper API versioning strategy ensures an API version remains functional when you enact changes on the code. It also means that API...
Read more >Versioning | SwaggerHub Documentation - SmartBear Support
All the versions are listed in the dropdown next to the API (domain) name, so you can switch between the versions with just...
Read more >API Versioning: What Is It and Why Is It So Hard?
First, do no harm. A smart strategy for versioning APIs means building in support for compatible changes from the very start.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@JoshLitt should be fixed now with the next release (see later PR merged)
I just ran into same issue with d-m-p 0.28 to 0.30 running against latest docker windows
How do fix this? my apology for not seeing the obvious in this discussion