[
https://issues.jboss.org/browse/JBIDE-22734?page=com.atlassian.jira.plugi...
]
Rick Wagner commented on JBIDE-22734:
-------------------------------------
When I started the CDK from a command line and 'vagrant up', the Docker components
did not autopopulate. (I had to try to answer the question "which socket should be
used for connection?")
The documentation did not provide a specific value. It suggested ""Add the
relevant socket information for your host. If you are unsure about this step, use the
default Unix socket Location value." Unfortunately, the documentation did not
suggest the useful command "vagrant service-manager env docker" which would have
given useful clues.
So I was stuck. I had to ask for help, which led me to find that starting via
'Servers view' allowed the Docker viewer to become automatically configured.
Please clarify CDK usage
------------------------
Key: JBIDE-22734
URL:
https://issues.jboss.org/browse/JBIDE-22734
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: cdk, docker
Environment: CDK, as used in DevStudio and installed via Development Suite.
Reporter: Rick Wagner
* * This use case may be attributable to user error. Please weigh implementation cost
accordingly. * *
After using the Development Suite installer, the user arrives in a newly installed
DevStudio instance but without clear instructions on how to use the CDK. In my first
attempt, I relied upon previous CDK experience and went to a command-line to start the CDK
with 'vagrant up'. This resulted in a failure of later DevStudio components.
The proper trail is to go to the 'Servers' tab in DevStudio to bring up the
environment. (Then DevStudio components like the Docker explorer will properly
self-configure. This does *not* happen when the CDK is brought up manually as I had
done.)
Please consider, look for ways to prevent other users from taking a similar path.
Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)