ERROR: client version 1.22 is too old #4106

PatrickLang · 2016-11-03T05:50:10Z

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

The text was updated successfully, but these errors were encountered:

nicholasdille · 2016-11-03T21:25:33Z

I am seeing the same issue then running docker-compose up on Windows Server 2016 RTM against a remote Windows Server 2016 RTM:
echo $env:DOCKER_HOST:

tcp://10.0.0.201:2375

docker-compose version:

docker-compose version 1.8.1, build 004ddae
docker-py version: 1.10.3
CPython version: 2.7.12
OpenSSL version: OpenSSL 1.0.2h  3 May 2016

docker version:

Client:
 Version:      1.12.2-cs2-ws-beta
 API version:  1.25
 Go version:   go1.7.1
 Git commit:   050b611
 Built:        Tue Oct 11 02:35:40 2016
 OS/Arch:      windows/amd64

Server:
 Version:      1.13.0-dev
 API version:  1.25
 Go version:   go1.7.3
 Git commit:   81683e8
 Built:        Thu Nov  3 15:40:00 2016
 OS/Arch:      windows/amd64

shin- · 2016-11-03T22:16:12Z

The Engine shouldn't refuse older clients. This is a wontfix as far as Compose is concerned - implications of changing the API version are too great.

nicholasdille · 2016-11-04T07:51:22Z

Isn't the message related to docker-py 1.10.5 which implements API version 1.22? Is it possible to update docker-py independently of docker-compose on Windows? Feels like I am missing something here ;-)

PatrickLang · 2016-11-05T04:52:44Z

Ok, I picked up builds of Docker/DockerD that have moby/moby#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 has version: '2'. Instead, I get this:

PS C:\Users\Patrick\Source\Repos\MusicStore> docker-compose -f .\docker-compose.windows.yml build
db uses an image, skipping
Building web
Traceback (most recent call last):
  File "<string>", line 3, in <module>
  File "compose\cli\main.py", line 65, in main
  File "compose\cli\main.py", line 117, in perform_command
  File "compose\cli\main.py", line 223, in build
  File "compose\project.py", line 300, in build
  File "compose\service.py", line 741, in build
  File "site-packages\docker\api\build.py", line 105, in build
  File "site-packages\docker\utils\decorators.py", line 47, in inner
  File "site-packages\docker\client.py", line 135, in _post
  File "site-packages\requests\sessions.py", line 522, in post
  File "site-packages\requests\sessions.py", line 475, in request
  File "site-packages\requests\sessions.py", line 596, in send
  File "site-packages\requests\adapters.py", line 423, in send
  File "site-packages\requests\packages\urllib3\connectionpool.py", line 595, in urlopen
  File "site-packages\requests\packages\urllib3\connectionpool.py", line 363, in _make_request
  File "httplib.py", line 1057, in request
  File "httplib.py", line 1097, in _send_request
  File "httplib.py", line 1053, in endheaders
  File "httplib.py", line 901, in _send_output
  File "httplib.py", line 870, in send
  File "site-packages\docker\transport\npipesocket.py", line 22, in wrapped
  File "site-packages\docker\transport\npipesocket.py", line 158, in sendall
  File "site-packages\docker\transport\npipesocket.py", line 22, in wrapped
  File "site-packages\docker\transport\npipesocket.py", line 153, in send
pywintypes.error: (232, 'WriteFile', 'The pipe is being closed.')
docker-compose returned -1

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:

PS C:\Users\Patrick\Source\Repos\MusicStore> docker-compose version
docker-compose version 1.9.0dev, build 9046e33
docker-py version: 1.10.6
CPython version: 2.7.12
OpenSSL version: OpenSSL 1.0.2h  3 May 2016
PS C:\Users\Patrick\Source\Repos\MusicStore> docker version
Client:
 Version:      1.13.0-dev
 API version:  1.25
 Go version:   go1.7.3
 Git commit:   c5ceb0f
 Built:        Sat Nov  5 03:24:43 2016
 OS/Arch:      windows/amd64

Server:
 Version:      1.13.0-dev
 API version:  1.25
 Go version:   go1.7.3
 Git commit:   c5ceb0f
 Built:        Sat Nov  5 03:24:43 2016
 OS/Arch:      windows/amd64
 Experimental: false

shin- · 2016-11-07T22:53:17Z

@PatrickLang It's possible build behaves a bit differently than other commands. Do you see the same issue with up or ps?

shin- · 2016-11-07T23:09:31Z

FWIW, I get the same type of error on Linux if I try to build with a version < 1.12

$ python
Python 2.7.9 (default, Apr  2 2015, 15:33:21) 
[GCC 4.9.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import docker
>>> c = docker.Client(version='1.11')
>>> c.build('.')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/joffrey/.envs/compose/local/lib/python2.7/site-packages/docker_py-1.10.6-py2.7.egg/docker/api/build.py", line 105, in build
    timeout=timeout,
  File "/home/joffrey/.envs/compose/local/lib/python2.7/site-packages/docker_py-1.10.6-py2.7.egg/docker/utils/decorators.py", line 47, in inner
    return f(self, *args, **kwargs)
  File "/home/joffrey/.envs/compose/local/lib/python2.7/site-packages/docker_py-1.10.6-py2.7.egg/docker/client.py", line 135, in _post
    return self.post(url, **self._set_request_timeout(kwargs))
  File "/home/joffrey/.envs/compose/local/lib/python2.7/site-packages/requests/sessions.py", line 508, in post
    return self.request('POST', url, data=data, json=json, **kwargs)
  File "/home/joffrey/.envs/compose/local/lib/python2.7/site-packages/requests/sessions.py", line 465, in request
    resp = self.send(prep, **send_kwargs)
  File "/home/joffrey/.envs/compose/local/lib/python2.7/site-packages/requests/sessions.py", line 573, in send
    r = adapter.send(request, **kwargs)
  File "/home/joffrey/.envs/compose/local/lib/python2.7/site-packages/requests/adapters.py", line 415, in send
    raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', error(104, 'Connection reset by peer'))

nerumo · 2016-12-05T07:16:41Z

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

nerumo · 2016-12-08T12:01:00Z

Nevermind my comment, after setting version to 2.1 it worked. But the error message could be a bit more specific

adamtuliper · 2016-12-08T13:38:08Z

FYI - tried 2.1 and it fixed the issue for me. Thanks :)

PatrickLang · 2016-12-09T07:24:57Z

I still get the error trying to build a docker-compose.yml with version: "2.0" using Docker version v1.13-rc3 too.

shin- · 2016-12-09T19:41:16Z

@PatrickLang Yes - you have to use 2.1 on Windows.

PatrickLang · 2016-12-09T19:49:13Z

@shin- should we close this issue? I think we should still fix the error message to say "Windows requires version 2.1 or greater" instead of

PS C:\Users\Patrick\Source\Repos\MusicStore> docker-compose -f .\docker-compose.windows.yml build
db uses an image, skipping
Building web
Traceback (most recent call last):
  File "<string>", line 3, in <module>
  File "compose\cli\main.py", line 65, in main
  File "compose\cli\main.py", line 117, in perform_command
  File "compose\cli\main.py", line 223, in build
  File "compose\project.py", line 300, in build
  File "compose\service.py", line 741, in build
  File "site-packages\docker\api\build.py", line 105, in build
  File "site-packages\docker\utils\decorators.py", line 47, in inner
  File "site-packages\docker\client.py", line 135, in _post
  File "site-packages\requests\sessions.py", line 522, in post
  File "site-packages\requests\sessions.py", line 475, in request
  File "site-packages\requests\sessions.py", line 596, in send
  File "site-packages\requests\adapters.py", line 423, in send
  File "site-packages\requests\packages\urllib3\connectionpool.py", line 595, in urlopen
  File "site-packages\requests\packages\urllib3\connectionpool.py", line 363, in _make_request
  File "httplib.py", line 1057, in request
  File "httplib.py", line 1097, in _send_request
  File "httplib.py", line 1053, in endheaders
  File "httplib.py", line 901, in _send_output
  File "httplib.py", line 870, in send
  File "site-packages\docker\transport\npipesocket.py", line 22, in wrapped
  File "site-packages\docker\transport\npipesocket.py", line 158, in sendall
  File "site-packages\docker\transport\npipesocket.py", line 22, in wrapped
  File "site-packages\docker\transport\npipesocket.py", line 153, in send
pywintypes.error: (232, 'WriteFile', 'The pipe is being closed.')
docker-compose returned -1

Should I file a separate issue for that and close this one?

shin- · 2016-12-09T19:54:40Z

pywintypes.error: (232, 'WriteFile', 'The pipe is being closed.')

That's an engine issue - the connection shouldn't be closed like this. It's a problem on Linux too as I mentioned here: #4106 (comment)

We can look into adding Windows checks with a distinct error message, but we have to differentiate Windows Engine from "Docker For Windows"

reduardo7 · 2017-02-16T17:53:47Z

Maybe related with: #268

Try to change version: "2" to "version: "2.1" in you docker-compose.yml file.

prochnowc · 2017-02-17T06:44:06Z

@shin- I still get the error when running docker-compose on docker for windows.

version: '2.1'

PS C:\> docker-compose version
docker-compose version 1.11.1, build 7afaa436
docker-py version: 2.0.2
CPython version: 2.7.13
OpenSSL version: OpenSSL 1.0.2j  26 Sep 2016

PS C:\dev\Source\DevTools\Docker> docker version
Client:
 Version:      1.13.1
 API version:  1.26
 Go version:   go1.7.5
 Git commit:   092cba3
 Built:        Wed Feb  8 08:47:51 2017
 OS/Arch:      windows/amd64

Server:
 Version:      1.13.1
 API version:  1.26 (minimum version 1.24)
 Go version:   go1.7.5
 Git commit:   092cba3
 Built:        Wed Feb  8 08:47:51 2017
 OS/Arch:      windows/amd64
 Experimental: true

PS C:\dev\Source\DevTools\Docker> docker-compose -f .\docker-compose.windows.yml build
consul uses an image, skipping
sql uses an image, skipping
Building audittrail
Traceback (most recent call last):
  File "docker-compose", line 3, in <module>
  File "compose\cli\main.py", line 88, in main
  File "compose\cli\main.py", line 140, in perform_command
  File "compose\cli\main.py", line 247, in build
  File "compose\project.py", line 313, in build
  File "compose\service.py", line 804, in build
  File "site-packages\docker\api\build.py", line 205, in build
  File "site-packages\docker\utils\decorators.py", line 47, in inner
  File "site-packages\docker\api\client.py", line 175, in _post
  File "site-packages\requests\sessions.py", line 522, in post
  File "site-packages\requests\sessions.py", line 475, in request
  File "site-packages\requests\sessions.py", line 596, in send
  File "site-packages\requests\adapters.py", line 423, in send
  File "site-packages\requests\packages\urllib3\connectionpool.py", line 595, in urlopen
  File "site-packages\requests\packages\urllib3\connectionpool.py", line 363, in _make_request
  File "httplib.py", line 1042, in request
  File "httplib.py", line 1082, in _send_request
  File "httplib.py", line 1038, in endheaders
  File "httplib.py", line 886, in _send_output
  File "httplib.py", line 855, in send
  File "site-packages\docker\transport\npipesocket.py", line 22, in wrapped
  File "site-packages\docker\transport\npipesocket.py", line 159, in sendall
  File "site-packages\docker\transport\npipesocket.py", line 22, in wrapped
  File "site-packages\docker\transport\npipesocket.py", line 154, in send
pywintypes.error: (232, 'WriteFile', 'The pipe is being closed.')
Failed to execute script docker-compose

aberlin75 · 2017-03-09T23:56:29Z

Same happen in VS2017 with docker 1.26 client version, I'll try to fix it changing .yml files version to '2.1' but still same error occurs.

1>------ Operación Compilar iniciada: proyecto: docker-compose, configuración: Debug Any CPU ------
1>docker-compose -f "c:\users\aberlin\documents\visual studio 2017\Projects\WebApplication1\docker-compose.yml" -f "c:\users\aberlin\documents\visual studio 2017\Projects\WebApplication1\docker-compose.override.yml" -f "c:\users\aberlin\documents\visual studio 2017\Projects\WebApplication1\docker-compose.vs.debug.yml" -p dockercompose3258359292 config
1>networks: {}
1>services:
1> webapplication1:
1> build:
1> args:
1> source: obj/Docker/empty/
1> context: c:\users\aberlin\documents\visual studio 2017\Projects\WebApplication1\WebApplication1
1> dockerfile: Dockerfile
1> entrypoint: tail -f /dev/null
1> environment:
1> ASPNETCORE_ENVIRONMENT: Development
1> DOTNET_USE_POLLING_FILE_WATCHER: '1'
1> image: webapplication1:dev
1> labels:
1> com.microsoft.visualstudio.targetoperatingsystem: linux
1> ports:
1> - '80'
1> volumes:
1> - c:\users\aberlin\documents\visual studio 2017\Projects\WebApplication1\WebApplication1:/app:rw
1> - C:\Users\aberlin\clrdbg:/clrdbg:ro
1> - C:\Users\aberlin.nuget\packages:/root/.nuget/packages:ro
1>version: '2.1'
1>volumes: {}
1>docker ps --filter "status=running" --filter "name=dockercompose3258359292_webapplication1_" --format {{.ID}} -n 1
1>WebApplication1 -> c:\users\aberlin\documents\visual studio 2017\Projects\WebApplication1\WebApplication1\bin\Debug\netcoreapp1.1\WebApplication1.dll
1>C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NonInteractive -NoProfile -WindowStyle Hidden -ExecutionPolicy RemoteSigned -File "C:\Users\aberlin\AppData\Local\Temp\GetClrDbg.ps1" -Version latest -RuntimeID debian.8-x64 -InstallPath "C:\Users\aberlin\clrdbg"
1>Info: Using clrdbg version '15.0.26022.0'
1>Info: Using Runtime ID 'debian.8-x64'
1>Info: Latest version of ClrDbg is present. Skipping downloads
1>docker-compose -f "c:\users\aberlin\documents\visual studio 2017\Projects\WebApplication1\docker-compose.yml" -f "c:\users\aberlin\documents\visual studio 2017\Projects\WebApplication1\docker-compose.override.yml" -f "c:\users\aberlin\documents\visual studio 2017\Projects\WebApplication1\docker-compose.vs.release.yml" -p dockercompose3258359292 kill
1>docker-compose -f "c:\users\aberlin\documents\visual studio 2017\Projects\WebApplication1\docker-compose.yml" -f "c:\users\aberlin\documents\visual studio 2017\Projects\WebApplication1\docker-compose.override.yml" -f "c:\users\aberlin\documents\visual studio 2017\Projects\WebApplication1\docker-compose.vs.release.yml" -p dockercompose3258359292 down --rmi local --remove-orphans
1>Removing network dockercompose3258359292_default
1>Network dockercompose3258359292_default not found.
1>docker-compose -f "c:\users\aberlin\documents\visual studio 2017\Projects\WebApplication1\docker-compose.yml" -f "c:\users\aberlin\documents\visual studio 2017\Projects\WebApplication1\docker-compose.override.yml" -f "c:\users\aberlin\documents\visual studio 2017\Projects\WebApplication1\docker-compose.vs.debug.yml" -p dockercompose3258359292 kill
1>docker-compose -f "c:\users\aberlin\documents\visual studio 2017\Projects\WebApplication1\docker-compose.yml" -f "c:\users\aberlin\documents\visual studio 2017\Projects\WebApplication1\docker-compose.override.yml" -f "c:\users\aberlin\documents\visual studio 2017\Projects\WebApplication1\docker-compose.vs.debug.yml" -p dockercompose3258359292 down --rmi local --remove-orphans
1>Removing network dockercompose3258359292_default
1>Network dockercompose3258359292_default not found.
1>docker-compose -f "c:\users\aberlin\documents\visual studio 2017\Projects\WebApplication1\docker-compose.yml" -f "c:\users\aberlin\documents\visual studio 2017\Projects\WebApplication1\docker-compose.override.yml" -f "c:\users\aberlin\documents\visual studio 2017\Projects\WebApplication1\docker-compose.vs.debug.yml" -p dockercompose3258359292 up -d --build
1>Creating network "dockercompose3258359292_default" with the default driver
1>HNS failed with error : Unspecified error
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Docker\Microsoft.VisualStudio.Docker.Compose.targets(192,5): error MSB4018: Error inesperado en la tarea "PrepareForLaunch".
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Docker\Microsoft.VisualStudio.Docker.Compose.targets(192,5): error MSB4018: Microsoft.DotNet.Docker.CommandLineClientException: Creating network "dockercompose3258359292_default" with the default driver
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Docker\Microsoft.VisualStudio.Docker.Compose.targets(192,5): error MSB4018: HNS failed with error : Unspecified error.
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Docker\Microsoft.VisualStudio.Docker.Compose.targets(192,5): error MSB4018:
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Docker\Microsoft.VisualStudio.Docker.Compose.targets(192,5): error MSB4018: Para más información de solución de problemas, vaya a http://aka.ms/DockerToolsTroubleshooting ---> Microsoft.DotNet.Docker.CommandLineClientException: Creating network "dockercompose3258359292_default" with the default driver
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Docker\Microsoft.VisualStudio.Docker.Compose.targets(192,5): error MSB4018: HNS failed with error : Unspecified error
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Docker\Microsoft.VisualStudio.Docker.Compose.targets(192,5): error MSB4018: en System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Docker\Microsoft.VisualStudio.Docker.Compose.targets(192,5): error MSB4018: en System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Docker\Microsoft.VisualStudio.Docker.Compose.targets(192,5): error MSB4018: en Microsoft.DotNet.Docker.DockerComposeClient.d__18.MoveNext()
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Docker\Microsoft.VisualStudio.Docker.Compose.targets(192,5): error MSB4018: --- Fin del seguimiento de la pila de la excepción interna ---
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Docker\Microsoft.VisualStudio.Docker.Compose.targets(192,5): error MSB4018: en Microsoft.DotNet.Docker.DockerComposeClient.d__18.MoveNext()
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Docker\Microsoft.VisualStudio.Docker.Compose.targets(192,5): error MSB4018: --- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción ---
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Docker\Microsoft.VisualStudio.Docker.Compose.targets(192,5): error MSB4018: en System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Docker\Microsoft.VisualStudio.Docker.Compose.targets(192,5): error MSB4018: en System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Docker\Microsoft.VisualStudio.Docker.Compose.targets(192,5): error MSB4018: en Microsoft.DotNet.Docker.DockerWorkspace.d__14.MoveNext()
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Docker\Microsoft.VisualStudio.Docker.Compose.targets(192,5): error MSB4018: --- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción ---
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Docker\Microsoft.VisualStudio.Docker.Compose.targets(192,5): error MSB4018: en System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Docker\Microsoft.VisualStudio.Docker.Compose.targets(192,5): error MSB4018: en System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Docker\Microsoft.VisualStudio.Docker.Compose.targets(192,5): error MSB4018: en Microsoft.DotNet.Docker.BuildTasks.DockerBaseTask.Execute()
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Docker\Microsoft.VisualStudio.Docker.Compose.targets(192,5): error MSB4018: en Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Docker\Microsoft.VisualStudio.Docker.Compose.targets(192,5): error MSB4018: en Microsoft.Build.BackEnd.TaskBuilder.d__26.MoveNext()
1>Compilación del proyecto "docker-compose.dcproj" terminada -- ERROR.
========== Compilar: 0 correctos o actualizados, 1 incorrectos, 0 omitidos ==========

shin- · 2017-03-10T00:04:44Z

@aberlin75 That error seems unrelated. Looks like a network issue similar to #4482

…se up (see docker/compose#4106)

…ersion is 1.2x As docker/compose#4106 states, the change to '2.1' fixes the following error, when running 'docker-compose up': ERROR: client version 1.2x is too old. Minimum supported API version is 1.2x, please upgrade your client to a newer version

…ersion is 1.2x (#576) As docker/compose#4106 states, the change to '2.1' fixes the following error, when running 'docker-compose up': ERROR: client version 1.2x is too old. Minimum supported API version is 1.2x, please upgrade your client to a newer version

Set docker-compose.yml version to 2.1 to fix a strange issue on Windows. See: docker/compose#4106 This may not occur anymore since we finally used docker-for-windows instead of the preinstalled docker in AppVeyor's VS2017 image. We also don't need to `DockerCli -SwitchDaemon`.

nikoo56 · 2017-07-05T18:07:59Z

I am getting same error when I change the version in compose file to 2.1 I am getting this error: Creating network with default driver HNS failed with error: The parameter is incorrect. I am using vs2017, Windows container, Windows 10.

David-Paterson · 2017-07-06T21:06:50Z

I am also getting this error when I change to 2.1 (Windows 10 + VS 2017 Latest Docker + Windows Container)

Severity Code Description Project File Line Suppression State
Error MSB4018 The "PrepareForLaunch" task failed unexpectedly.
Microsoft.DotNet.Docker.CommandLineClientException: Creating network "dockercompose2647930274_default" with the default driver
HNS failed with error : The parameter is incorrect. .

For more troubleshooting information, go to http://aka.ms/DockerToolsTroubleshooting ---> Microsoft.DotNet.Docker.CommandLineClientException: Creating network "dockercompose2647930274_default" with the default driver
HNS failed with error : The parameter is incorrect.
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DotNet.Docker.DockerComposeClient.d__18.MoveNext()
--- End of inner exception stack trace ---
at Microsoft.DotNet.Docker.DockerComposeClient.d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DotNet.Docker.DockerWorkspace.d__14.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DotNet.Docker.BuildTasks.DockerBaseTask.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.d__26.MoveNext() docker-compose C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Microsoft\VisualStudio\v15.0\Docker\Microsoft.VisualStudio.Docker.Compose.targets 192

shin- · 2017-07-06T21:11:01Z

@David-Paterson @hugo1337 - This is a networking issue on Docker Windows, not a Compose issue. See #4482 and moby/moby#30280

shin- · 2017-07-06T21:13:30Z

I'll close this issue as the original problem has been fixed and it is generating a lot of noise.
I'll create a separate issue to address #4106 (comment)

lilithebowman · 2017-08-31T15:56:46Z

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 version
Client:
 Version:      17.06.1-ce
 API version:  1.30
 Go version:   go1.8.3
 Git commit:   874a737
 Built:        Thu Aug 17 22:48:20 2017
 OS/Arch:      windows/amd64

Server:
 Version:      17.06.1-ce
 API version:  1.30 (minimum version 1.24)
 Go version:   go1.8.3
 Git commit:   874a737
 Built:        Thu Aug 17 23:03:03 2017
 OS/Arch:      windows/amd64
 Experimental: true

$ docker-compose version
docker-compose version 1.14.0, build c7bdf9e3
docker-py version: 2.3.0
CPython version: 2.7.13
OpenSSL version: OpenSSL 1.0.2j  26 Sep 2016

$ docker-compose up
client version 1.21 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version

docker-compose.yml:

version: '2.1'

volumes:
    database_data:
        driver: local

services:
  nginx:
      image: nginx:latest
      ports:
          - 8080:80
      volumes:
          - ./docker/nginx/default.conf:/etc/nginx/conf.d/default.conf
      volumes_from:
          - php
  php:
      build: ./docker/php/
      expose:
          - 9000
      volumes:
          - .:/var/www/html
  mysql:
      image: mysql:latest
      expose:
          - 3306
      volumes:
          - database_data:/var/lib/mysql
      environment:
          MYSQL_ROOT_PASSWORD: secret
          MYSQL_DATABASE: project
          MYSQL_USER: project
          MYSQL_PASSWORD: project

lilithebowman · 2017-08-31T15:58:01Z

^^^ This is a fresh new install, and my first docker experience.

How is this easier again?

tapasudenia · 2017-12-13T16:04:12Z

Hi Guys,
I am getting this error

Error MSB4018 The "PrepareForLaunch" task failed unexpectedly.
Microsoft.DotNet.Docker.CommandLineClientException: client version 1.22 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version

My Environment

Windows 10
Visual Studio 2015 with Docker support extension

docker version
Client:
Version: 17.09.0-ce
API version: 1.32
Go version: go1.8.3
Git commit: afdb6d4
Built: Tue Sep 26 22:40:09 2017
OS/Arch: windows/amd64

Server:
Version: 17.09.0-ce
API version: 1.32 (minimum version 1.24)
Go version: go1.8.3
Git commit: afdb6d4
Built: Tue Sep 26 22:50:27 2017
OS/Arch: windows/amd64
Experimental: true

docker-compose version
docker-compose version 1.16.1, build 6d1ac21
docker-py version: 2.5.1
CPython version: 2.7.13
OpenSSL version: OpenSSL 1.0.2j 26 Sep 2016

How do I change the version to 2.x? Any other fix?

Thanks.

tapasudenia · 2017-12-13T16:27:00Z

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

matas-valuzis · 2018-01-09T23:06:41Z

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.

lilithebowman · 2018-01-10T04:09:16Z

smacks forehead
WHAT?!
Really?!

lilithebowman · 2018-01-10T04:10:13Z

I mean, I haven't installed this again anyway since HyperV prevents me from creating other VMs on the machine. So... that's pretty garbage.

skrishnablockchain · 2018-06-19T15:11:19Z

My Environment

Windows 10

docker version
Client:
Version: 18.05.0-ce
API version: 1.37
Go version: go1.9.5
Git commit: f150324
Built: Wed May 9 22:12:05 2018
OS/Arch: windows/amd64
Experimental: false
Orchestrator: swarm

Server:
Engine:
Version: 18.05.0-ce
API version: 1.37 (minimum version 1.24)
Go version: go1.10.1
Git commit: f150324
Built: Wed May 9 22:29:00 2018
OS/Arch: windows/amd64
Experimental: true

client version 1.22 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version
ERROR !!!! Unable to start network

Please let me know the error resolve details.

wessRibeiro · 2018-07-25T14:04:26Z

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

felipemarques · 2019-04-20T01:07:50Z

an advantage in use Windows containers is: low memory used ... when we use linux containers ... the hyper-v starts an virtual machine with 2gb memory. Why docker-compose does not work with windows containers ?

felipemarques · 2019-04-20T01:08:49Z

This is the error for me...

DavyGuedes · 2019-05-20T20:36:50Z

Hi @felipemarques.
Have you enabled "Experimental Features" in the Daemon section in the Docker for Windows settings? By doing this I was able to pull and run images based on linux with Windows Containers enabled.

Windows 10 Pro 1809
Docker version 18.09.2, build 6247962
docker-compose version 1.23.2, build 1110ad0
(Windows Containers enabled)

girishgodage · 2019-06-28T11:20:03Z

Switch to Linux Container is help me to resolve the issue

PatrickLang mentioned this issue Nov 5, 2016

Windows: Allow API v1.24 moby/moby#28072

Merged

PatrickLang mentioned this issue Nov 5, 2016

Updating docker-compose.yml version to 2.1 friism/MusicStore#3

Merged

shin- added the group/windows-server label Nov 7, 2016

jonashackt added a commit to jonashackt/cxf-spring-cloud-netflix-docker that referenced this issue Mar 14, 2017

Fixing 'docker-compose client to old windows' error with docker-compo…

3482c7b

…se up (see docker/compose#4106)

jonashackt mentioned this issue Mar 14, 2017

Fixing ERROR: client version 1.2x is too old. Minimum supported API version is 1.2x MicrosoftDocs/Virtualization-Documentation#576

Merged

JanneRantala mentioned this issue Mar 24, 2017

Support docker compose 2.1 microsoft/vsts-docker#31

Open

shin- closed this as completed Jul 6, 2017

shin- mentioned this issue Jul 6, 2017

docker-compose build on Windows fails with stacktrace if API version < 1.24 #5005

Closed

JacobMillward mentioned this issue Jul 26, 2017

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

Closed

shin- mentioned this issue Aug 14, 2017

client version 1.22 is too old. Minimum supported API version is 1.25 #5103

Closed

lienze87 mentioned this issue Jan 23, 2018

ERROR: client version 1.22 is too old easychen/fangPHP#3

Closed

gtaspider mentioned this issue Mar 23, 2018

Service 'app' failed to build on Windows Server 2019 mattermost/mattermost-docker#252

Closed

RobinFischer mentioned this issue Apr 10, 2018

Windows docker compose version too old ScaleIT-Org/ionic-app-skeleton#17

Closed

SolsWebdesign mentioned this issue Jun 6, 2018

client 1.21 version too old when trying to get docker to run andreaskoch/dockerized-magento#53

Closed

sscaling mentioned this issue Feb 15, 2019

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

Open

bamthomas mentioned this issue Nov 7, 2019

[windows] error running datashare ICIJ/datashare#300

Closed

ChristianMurphy mentioned this issue Nov 12, 2019

Client version 1.21 is too old. Minimum supported API version is 1.24 openmhealth/shimmer#112

Open

nmirasch mentioned this issue Feb 13, 2020

Fix docker compose for macos kiegroup/kogito-travel-agency-tutorial#3

Merged

Pr3d4dor referenced this issue in RamonSilva20/mapos Apr 11, 2020

Adicionado função de dump para facilitar o desenvolvimento

060f950

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ERROR: client version 1.22 is too old #4106

ERROR: client version 1.22 is too old #4106

PatrickLang commented Nov 3, 2016

nicholasdille commented Nov 3, 2016

shin- commented Nov 3, 2016

nicholasdille commented Nov 4, 2016

PatrickLang commented Nov 5, 2016 •

edited

Loading

shin- commented Nov 7, 2016

shin- commented Nov 7, 2016

nerumo commented Dec 5, 2016

nerumo commented Dec 8, 2016

adamtuliper commented Dec 8, 2016

PatrickLang commented Dec 9, 2016 •

edited

Loading

shin- commented Dec 9, 2016

PatrickLang commented Dec 9, 2016

shin- commented Dec 9, 2016

reduardo7 commented Feb 16, 2017

prochnowc commented Feb 17, 2017

aberlin75 commented Mar 9, 2017 •

edited

Loading

shin- commented Mar 10, 2017

nikoo56 commented Jul 5, 2017

David-Paterson commented Jul 6, 2017 •

edited

Loading

shin- commented Jul 6, 2017

shin- commented Jul 6, 2017

lilithebowman commented Aug 31, 2017

lilithebowman commented Aug 31, 2017

tapasudenia commented Dec 13, 2017

tapasudenia commented Dec 13, 2017

matas-valuzis commented Jan 9, 2018

lilithebowman commented Jan 10, 2018

lilithebowman commented Jan 10, 2018

skrishnablockchain commented Jun 19, 2018

wessRibeiro commented Jul 25, 2018

felipemarques commented Apr 20, 2019

felipemarques commented Apr 20, 2019

DavyGuedes commented May 20, 2019

girishgodage commented Jun 28, 2019

ERROR: client version 1.22 is too old #4106

ERROR: client version 1.22 is too old #4106

Comments

PatrickLang commented Nov 3, 2016

nicholasdille commented Nov 3, 2016

shin- commented Nov 3, 2016

nicholasdille commented Nov 4, 2016

PatrickLang commented Nov 5, 2016 • edited Loading

shin- commented Nov 7, 2016

shin- commented Nov 7, 2016

nerumo commented Dec 5, 2016

nerumo commented Dec 8, 2016

adamtuliper commented Dec 8, 2016

PatrickLang commented Dec 9, 2016 • edited Loading

shin- commented Dec 9, 2016

PatrickLang commented Dec 9, 2016

shin- commented Dec 9, 2016

reduardo7 commented Feb 16, 2017

prochnowc commented Feb 17, 2017

aberlin75 commented Mar 9, 2017 • edited Loading

shin- commented Mar 10, 2017

nikoo56 commented Jul 5, 2017

David-Paterson commented Jul 6, 2017 • edited Loading

shin- commented Jul 6, 2017

shin- commented Jul 6, 2017

lilithebowman commented Aug 31, 2017

lilithebowman commented Aug 31, 2017

tapasudenia commented Dec 13, 2017

tapasudenia commented Dec 13, 2017

matas-valuzis commented Jan 9, 2018

lilithebowman commented Jan 10, 2018

lilithebowman commented Jan 10, 2018

skrishnablockchain commented Jun 19, 2018

wessRibeiro commented Jul 25, 2018

felipemarques commented Apr 20, 2019

felipemarques commented Apr 20, 2019

DavyGuedes commented May 20, 2019

girishgodage commented Jun 28, 2019

PatrickLang commented Nov 5, 2016 •

edited

Loading

PatrickLang commented Dec 9, 2016 •

edited

Loading

aberlin75 commented Mar 9, 2017 •

edited

Loading

David-Paterson commented Jul 6, 2017 •

edited

Loading