Engine-api built with Go(<=1.4) won't work with Docker daemon built with Go(>=1.6) about engine-api HOT 8 CLOSED

See moby/moby#20865

from engine-api.

@duglin Yeah, I saw that one. :)

I think in moby/moby#20865, people were mainly talking about the Docker CLI. While this one is just talking about the engine-api, which is a little different:

1. People may use engine-api to build anything, they may need to use Go 1.4 for some reason.
2. This issue is easier to fix because it's only about engine-api, I don't think it will affect too many people.

from engine-api.

I do agree with @Random-Liu, maybe we should handle this in here too.
/cc @calavera @MHBauer

from engine-api.

Thanks, @vdemeester!

BTW, we are switching from go-dockerclient to this official engine-api, :). There is no such problem in go-dockerclient (See here)

from engine-api.

We have control of the default client, so we should be able to handle it. Is there a way uses of engine-api can work around this by providing a customized client? We should work out both ways, if possible.

from engine-api.

Explicitly setting the value to something meaningful and valid should be easy enough to do. A PR would be welcome....

from engine-api.

@duglin Thanks, I'll send a PR soon :)

from engine-api.

Fixed by #190.

from engine-api.