Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR: client version 1.22 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version #461

Open
wenfengsui opened this issue Feb 15, 2019 · 13 comments
Labels

Comments

@wenfengsui
Copy link

the error happened after upgrade window docker desktop to the latest.

the workaround is increase version of docker-compose file.

@wenfengsui
Copy link
Author

i have created pull request #462

@sscaling
Copy link
Collaborator

sscaling commented Feb 15, 2019

This error message would indicate a client error, not a docker compose version error. I would expect upgrading your docker client is the required fix, not changing the docker compose version. Version '2.0' has been supported from docker engine 1.10.0 onwards. ref: https://docs.docker.com/compose/compose-file/compose-versioning/#compatibility-matrix

I am curious why upgrading the docker-compose version appears to fix this for you? Perhaps a bug in the windows client implementation?

@sscaling
Copy link
Collaborator

A quick google finds similar issues which indicate a bug in the Windows implementation. Did you try anything like 'Switch to linux containers' (docker/compose#4106 (comment)) ?

@HQebupt
Copy link

HQebupt commented Mar 1, 2019

'Switch to linux containers' does not work. It will occure an error:

Unable to create: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Hyper-V encountered an error trying to access an object on computer 'CNENHUANGQ1L2C' because the object was not found. The object might have been deleted. Verify that the Virtual Machine Management service on the computer is running.
at New-Switch, <No file>: line 121
at <ScriptBlock>, <No file>: line 411
   at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters) in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeClient.cs:line 36
   at Docker.Actions.<>c__DisplayClass28_0.<SwitchDaemon>b__0() in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 305
   at Docker.WPF.TaskQueue.<>c__DisplayClass19_0.<.ctor>b__1() in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:line 59

@sscaling
Copy link
Collaborator

sscaling commented Mar 1, 2019

@HQebupt - sounds like a Docker on windows issue rather than anything to do with this image.

@cbaurand
Copy link

cbaurand commented Jun 6, 2019

It's still not working. Any news about this problem?

@StayHomeThereIsNoFrance
Copy link

It's still not working. Any news about this problem?

put in the head of docker-compose:

version: '2.4'

it helped me

@iNithinPrasad
Copy link

You have 2 options here

  1. Check if you are using the wrong/incompatible OS for the image. If so switch your OS in docker desktop and try once more.
  2. Change the docker compose version tag to 2.4 as the original version is not updated.

@srungta
Copy link

srungta commented Feb 13, 2020

It started working for me after switching to Linux containers on Win 10

@filatan
Copy link

filatan commented Jun 4, 2020

A quick google finds similar issues which indicate a bug in the Windows implementation. Did you try anything like 'Switch to linux containers' (docker/compose#4106 (comment)) ?

This worked fine for me...Thanks

dirkpape added a commit to dirkpape/Docker-DocumentServer that referenced this issue Feb 18, 2024
@sahumino
Copy link

i have created pull request #462

This solution saved my day. Thank you.

@wbanchon
Copy link

Todavía no funciona. ¿Alguna noticia sobre este problema?

poner en la cabeza de docker-compose:

version: '2.4'

Me ayudó

Perfecto, esto funcionó en un ambiente de Linux

@bendene12
Copy link

Thank you @StayHomeThereIsNoFrance !
Your suggestion worked for me big time!

tamascsaba added a commit to tamascsaba/http-observatory that referenced this issue Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests