> I didn't use the 'Servers' view to start the CDK and went off to manipulate it from the command line
Mind listing those steps in a jira? Ideally, we should be able to handle user error gracefully without botching up the works, so steps to replicate may help me understand how the uninformed user may make a mess of things ;) On Tue, Jul 12, 2016 at 11:31 AM, Rick Wagner <[email protected]> wrote: > Hello All, > > Many thanks for these great tips, the Development Suite has performed > flawlessly. (The fault was mine. I didn't use the 'Servers' view to start > the CDK and went off to manipulate it from the command line. When I used > the Developer Studio provided tools, everything just worked.) > > Thanks, > > Rick > > > On Tue, Jul 12, 2016 at 4:27 AM, Hardy Ferentschik <[email protected]> > wrote: > >> Hi, >> >> On Tue, 12-Jul-2016 11:25, Praveen Kumar wrote: >> > On Tue, Jul 12, 2016 at 11:08 AM, Pete Muir <[email protected]> wrote: >> > > tcp://10.1.2.2:2375 >> > >> > Pete, I think development suite get those details (docker env to >> > connect external tooling) from vagrant service manager. >> >> +1 Also my understanding. There should really nothing be to be configured. >> It might be that the CDK did not boot/start correctly or something else >> went >> wrong. Would be interesting to know whether the CDK is up and running and >> whether 'vagrant service-manager env' returns the DOCKER settings. >> >> --Hardy >> >> > > _______________________________________________ > Devtools mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/devtools > >
_______________________________________________ Devtools mailing list [email protected] https://www.redhat.com/mailman/listinfo/devtools
