compose: ERROR: client version 1.22 is too old
I’m trying to run https://github.com/docker/labs/blob/master/windows/windows-containers/MultiContainerApp.md using Docker-Compose with named pipes. It’s failing with an error about client API version:
PS C:\Source\Musicstore> docker-compose -f .\docker-compose.windows.yml up
ERROR: client version 1.22 is too old. Minimum supported API version is 1.25, please upgrade your client to a newer version
PS C:\Source\Musicstore> docker-compose -f .\docker-compose.windows.yml ps
ERROR: client version 1.22 is too old. Minimum supported API version is 1.25, please upgrade your client to a newer version
Here’s what I have installed:
docker-compose version
docker-compose version 1.9.0-rc2, build d41f869
docker-py version: 1.10.5
CPython version: 2.7.12
OpenSSL version: OpenSSL 1.0.2h 3 May 2016
docker version
:
Client:
Version: 1.13.0-dev
API version: 1.25
Go version: go1.7.3
Git commit: 877c860
Built: Thu Nov 3 04:06:20 2016
OS/Arch: windows/amd64
Server:
Version: 1.13.0-dev
API version: 1.25
Go version: go1.7.3
Git commit: 877c860
Built: Thu Nov 3 04:06:20 2016
OS/Arch: windows/amd64
Experimental: false
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 7
- Comments: 35
Commits related to this issue
- Fixing 'docker-compose client to old windows' error with docker-compose up (see https://github.com/docker/compose/issues/4106) — committed to jonashackt/cxf-spring-cloud-netflix-docker by jonashackt 7 years ago
- Fixing ERROR: client version 1.2x is too old. Minimum supported API version is 1.2x As https://github.com/docker/compose/issues/4106 states, the change to '2.1' fixes the following error, when runnin... — committed to jonashackt/Virtualization-Documentation by jonashackt 7 years ago
- Fixing ERROR: client version 1.2x is too old. Minimum supported API version is 1.2x (#576) As https://github.com/docker/compose/issues/4106 states, the change to '2.1' fixes the following error, when... — committed to MicrosoftDocs/Virtualization-Documentation by jonashackt 7 years ago
- build: Run unit tests on AppVeyor Set docker-compose.yml version to 2.1 to fix a strange issue on Windows. See: https://github.com/docker/compose/issues/4106 This may not occur anymore since we fina... — committed to cozy-labs/cozy-desktop by sebn 7 years ago
- build: Run unit tests on AppVeyor Set docker-compose.yml version to 2.1 to fix a strange issue on Windows. See: https://github.com/docker/compose/issues/4106 This may not occur anymore since we fina... — committed to cozy-labs/cozy-desktop by sebn 7 years ago
- build: Run unit tests on AppVeyor Set docker-compose.yml version to 2.1 to fix a strange issue on Windows. See: https://github.com/docker/compose/issues/4106 This may not occur anymore since we fina... — committed to cozy-labs/cozy-desktop by sebn 7 years ago
- build: Run unit tests on AppVeyor Set docker-compose.yml version to 2.1 to fix a strange issue on Windows. See: https://github.com/docker/compose/issues/4106 This may not occur anymore since we fina... — committed to cozy-labs/cozy-desktop by sebn 7 years ago
- build: Run unit tests on AppVeyor Set docker-compose.yml version to 2.1 to fix a strange issue on Windows. See: https://github.com/docker/compose/issues/4106 This may not occur anymore since we fina... — committed to cozy-labs/cozy-desktop by sebn 7 years ago
- build: Run unit tests on AppVeyor Set docker-compose.yml version to 2.1 to fix a strange issue on Windows. See: https://github.com/docker/compose/issues/4106 This may not occur anymore since we fina... — committed to cozy-labs/cozy-desktop by sebn 7 years ago
- build: Run unit tests on AppVeyor Set docker-compose.yml version to 2.1 to fix a strange issue on Windows. See: https://github.com/docker/compose/issues/4106 This may not occur anymore since we fina... — committed to cozy-labs/cozy-desktop by sebn 7 years ago
- build: Run unit tests on AppVeyor Set docker-compose.yml version to 2.1 to fix a strange issue on Windows. See: https://github.com/docker/compose/issues/4106 This may not occur anymore since we fina... — committed to cozy-labs/cozy-desktop by sebn 7 years ago
- build: Run unit tests on AppVeyor Set docker-compose.yml version to 2.1 to fix a strange issue on Windows. See: https://github.com/docker/compose/issues/4106 This may not occur anymore since we fina... — committed to cozy-labs/cozy-desktop by sebn 7 years ago
- build: Run unit tests on AppVeyor Also set docker-compose.yml version to 2.1 to fix a strange issue on Windows. See: https://github.com/docker/compose/issues/4106 Although we don't use it on CI (runn... — committed to cozy-labs/cozy-desktop by sebn 7 years ago
- build: Run unit tests on AppVeyor Also set docker-compose.yml version to 2.1 to fix a strange issue on Windows. See: https://github.com/docker/compose/issues/4106 Although we don't use it on CI (runn... — committed to cozy-labs/cozy-desktop by sebn 7 years ago
- build: Run unit tests on AppVeyor Set up test env with remote Cozy instance (running linux containers on AppVeyor is not easy). Also set docker-compose.yml version to 2.1 to fix a strange issue on W... — committed to cozy-labs/cozy-desktop by sebn 7 years ago
- build: Run unit tests on AppVeyor Set up test env with remote Cozy instance (running linux containers on AppVeyor is not easy). Also set docker-compose.yml version to 2.1 to fix a strange issue on W... — committed to cozy-labs/cozy-desktop by sebn 7 years ago
- build: Run unit tests on AppVeyor Set up test env with remote Cozy instance (running linux containers on AppVeyor is not easy). Also set docker-compose.yml version to 2.1 to fix a strange issue on W... — committed to cozy-labs/cozy-desktop by sebn 7 years ago
- Update docker version in docker-compose.yml I was just trying to follow along with http://markheath.net/post/get-up-and-running-with-docker-for-windows and hit an error that led me to https://github.... — committed to rainabba/ndc-london-2017 by rainabba 7 years ago
- Adicionado função de dump para facilitar o desenvolvimento — committed to RamonSilva20/mapos by Pr3d4dor 4 years ago
Its kinda relevant and might help some people so I’m gonna post this here:
After recent “Docker for Windows” update or fresh install people get switched to
Windows containers
mode. If you are in this mode and try to run/build linux containers you’ll probably get errors like:client version 1.22 is too old. Minimum supported API version is 1.24, please up grade your client to a newer version
or
image operating system linux cannot be used
Make sure you switch to
Linux containers
mode if you want to use linux containers.Maybe related with: #268
Try to change
version: "2"
to"version: "2.1"
in youdocker-compose.yml
file.Ok, I picked up builds of Docker/DockerD that have docker/docker#28072 fixed.
Based on the discussion there - I think that I should still be getting
ERROR: client version 1.22 is too old. Minimum supported API version is 1.25, please upgrade your client
because the docker-compose file hasversion: '2'
. Instead, I get this:Why aren’t I getting the right error?
If I change it to
version: '2.1'
, then it works as expected.For reference, here’s the versions I’m using now:
Nevermind my comment, after setting version to 2.1 it worked. But the error message could be a bit more specific
^^^ This is a fresh new install, and my first docker experience.
How is this easier again?
@PatrickLang Yes - you have to use 2.1 on Windows.
I’m getting the same issue with
Client: Version: 1.13.0-rc2 API version: 1.25 Go version: go1.7.3 Git commit: 1f9b3ef Built: Wed Nov 23 17:40:58 2016 OS/Arch: windows/amd64
Server: Version: 1.13.0-rc2 API version: 1.25 Minimum API version: 1.24 Go version: go1.7.3 Git commit: 1f9b3ef Built: Wed Nov 23 17:40:58 2016 OS/Arch: windows/amd64 Experimental: false
Switch to Linux Container is help me to resolve the issue
FYI - tried 2.1 and it fixed the issue for me. Thanks 😃
@shin- I still get the error when running docker-compose on docker for windows.
version: '2.1'
Clique com o botão direito do mouse no icone do docker e escolha a opção “switch to linux containers” como mencionado mais acima dos comentários
Got it resolved by changing the version to 2.1 everywhere, in all the docker-compose files.
Now I am getting this error when I am trying to run docker for windows on windows host
Error: image operating system linux cannot be used
Any suggestions? Thanks
I’m not having success with setting version: ‘2.1’ on my docker-compose.yml
It still claims my version is 1.21 with a minimum version of 1.24
docker-compose.yml:
@aberlin75 That error seems unrelated. Looks like a network issue similar to #4482
I still get the error trying to build a docker-compose.yml with
version: "2.0"
using Docker version v1.13-rc3 too.