[linuxtools-dev] [Docker Tooling] launch "default" docker machine "automatically"

2016-06-29 Thread Tim Orling
In our typical usage, the customer will only have the "default" docker machine installed (could be Mac OSX, Windows or Linux host). Is there a preferred way to simply "automatically" connect to the "default" docker machine? Yes it only takes three mouse clicks to accomplish that, but some customers

Re: [linuxtools-dev] [Docker Tooling] launch "default" docker machine "automatically"

2016-06-30 Thread Tim Orling
Yes. Exactly what I meant. I suspect the environment variables will also change with the new Docker that is in beta testing. I have not had time to test it yet. IMHO, on startup we should check if Docker is running and if so connect to either the "default" machine or one which is defined in Prefer

Re: [linuxtools-dev] [Docker Tooling] launch "default" docker machine "automatically"

2016-07-06 Thread Tim Orling
On Mon, Jul 4, 2016 at 12:36 AM, Xavier Coulon wrote: > ok, sorry for the misunderstanding, Tim. I now see what you meant and I > like Roland's idea of using extensions to auto-detect connection upon > initialization. > I would add that it should be an option in the Docker tooling preferences > (

[linuxtools-dev] hudson job for docker tooling?

2016-07-27 Thread Tim Orling
I don't see that there is a hipp job for docker tooling site. It would be very helpful to be able to use the artifacts from a lastSuccessfulBuild of master, at least until 2.1.0 is released. Cheers! --Tim ___ linuxtools-dev mailing list linuxtools-dev@e

Re: [linuxtools-dev] hudson job for docker tooling?

2016-07-28 Thread Tim Orling
On Thu, Jul 28, 2016 at 6:21 AM, Roland Grunberg wrote: > > I don't see that there is a hipp job for docker tooling site. It would be > > very helpful to be able to use the artifacts from a lastSuccessfulBuild > of > > master, at least until 2.1.0 is released. > > Hi Tim, > > You're right that ou