Fork me on GitHub
#docker
<
2020-04-01
>
lispyclouds17:04:28

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

mkvlr17:04:43

this is the latest docker from fedora core os

mkvlr17:04:08

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

lispyclouds17:04:00

not sure, what does docker version say?

lispyclouds17:04:14

should show the max supported version

lispyclouds17:04:32

also you can pin 1.39 to the client too

mkvlr17:04:11

[[email protected] ~]$ 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

lispyclouds17:04:17

so this is older right? 1.40 is from docker 19

mkvlr17:04:30

yes, but why is it trying 1.40?

mkvlr17:04:47

something going wrong with the version detection?

lispyclouds17:04:48

by default it picks up the latest yaml

lispyclouds17:04:04

thats not implemented yet unfortunately 😞

mkvlr17:04:13

but it worked for older versions?

lispyclouds17:04:30

yeah you can pin the version you want to work with

mkvlr17:04:45

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

mkvlr17:04:46

API version:  1.32

lispyclouds17:04:04

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

lispyclouds19:04:03

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.

🙏 4