Hi, Hmm thats actually something we can try out. We will have to override existing docker client. For windows, on command prompt, we do have 'set' command as in 'set path='path/to/our/docker/binary' and it will only be valid for that one session.
On Fri, 2016-02-05 at 02:22 -0500, Bama Charan Kundu wrote: > Re-framed the reply. > > ----- Original Message ----- > > From: "Max Rydahl Andersen" <[email protected]> > > To: "Bama Charan Kundu" <[email protected]> > > Cc: "Lalatendu Mohanty" <[email protected]>, container-tools@redh > > at.com > > Sent: Thursday, February 4, 2016 9:55:57 PM > > Subject: Re: [Container-tools] Version incompatibility of Docker > > client and server - projectatomic/vagrant-adbinfo > > issue #85 > > > > On 4 Feb 2016, at 8:02, Bama Charan Kundu wrote: > > > > > My suggestion is to package equivalent docker client in the ADB > > > box ( > > > for Linux, OSX, Windows) and then we can expose these binaries > > > through > > > a > > > http server or equivalent. > > > > Is there a working docker native windows client yet ? > > AFAIK, I did not see docker native windows client, they have shifted > to docker toolbox. This tool box does all the setup related to docker > including boot2docker. > > > > > btw. on the topic of supporting multiple versions - the way we do > > it > > in Eclipse is that the spotify client we use don't perform the > > version > > check. > > > > So for now we survive on "luck". > > Does this mean that the API server of docker engine supports the > older > native clients also? > They are restricting to use older docker client by version check? > > > > > Down the road we might have to extend the client to make it handle > > differences between versions or in worst case bundle multiple > > client > > jars to be able to target both the slower moving CDK and the actual > > docker which most will use in the community. > > > > Yes, I believe we should not be dependent on the docker teams design. > we should put this in a way to work completely on our architecture. > I am going through the vagrant options we can adopt, trying to get > through this. > > Regards > Bamacharan > > > /max > > http://about.me/maxandersen > > > > _______________________________________________ > Container-tools mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/container-tools _______________________________________________ Container-tools mailing list [email protected] https://www.redhat.com/mailman/listinfo/container-tools
