One possibility which does not involve docker-machine is illustrated in issue 2159 on Azure:
I was able to work around this issue by DOCKER_API_VERSION
to match the server version and move ahead.
See this comment:
As of Docker 1.10, there is now support for the DOCKER_API_VERSION
environment variable that allows you to dictate which API version that the client should use.
As mentioned in docker issue 21930:
There are many times when the Docker version on a client can differ to that on a server.
This is typically because that end users are faster to update their clients whereas hosted Docker services or servers in production are slower to upgrade.
This issue can be much worse when attempting to RC test the new version of Docker as you need to switch Docker Client versions or set DOCKER_API_VERSION
.
The latter can have consequences e.g newer client features and flags failing against older engine versions.