Clojurians Log v2

https://user-images.githubusercontent.com/1663/78155243-7dc34e00-743d-11ea-8bdf-5407c65fe627.png

🤔 1.40 should be supported, right? https://github.com/lispyclouds/clj-docker-client/blob/master/resources/api/v1.40.yaml

maybe the engine is older? this is the version matrix https://docs.docker.com/engine/api/#api-version-matrix

@mkvlr

hmm

this is the latest docker from fedora core os

@rahul080327 could this be an issue with docker built from source?

not sure, what does docker version say?

should show the max supported version

also you can pin 1.39 to the client too

[core@runner-adshe-staging ~]$ docker version
Client:
 Version:           18.09.8
 API version:       1.39
 Go version:        go1.13beta1
 Git commit:        0dd43dd
 Built:             Fri Jul 26 03:04:01 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.09.8
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.13beta1
  Git commit:       0dd43dd
  Built:            Thu Jul 25 00:00:00 2019
  OS/Arch:          linux/amd64
  Experimental:     true

so this is older right? 1.40 is from docker 19

yes, but why is it trying 1.40?

something going wrong with the version detection?

by default it picks up the latest yaml

oh

thats not implemented yet unfortunately 😞

but it worked for older versions?

yeah you can pin the version you want to work with

we don’t pin a version, but have still an old version in production and there it works

API version:  1.32

thats odd, this picks up the latest when nothings specified when making the client

https://github.com/lispyclouds/clj-docker-client/blob/master/src/clj_docker_client/specs.clj#L22

this is solved. issue was the old version doesnt seem to check the version on the API but the new one does. pinning the version solved it.

@glfinn83 has joined the channel