[jbosstools-issues] [JBoss JIRA] (JBIDE-21947) Docker connection does not work after cdk restart

[Hardy Ferentschik (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-21947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182974#comment-13182974 ] 

Hardy Ferentschik commented on JBIDE-21947:
-------------------------------------------

{quote}
The linked issue implies it's 0.0.4.1 but is that true? 
{quote}

Not sure, no idea how to get _0.0.4.1_, except maybe building from source. I added a comment to the issue that a proper release is needed which also gets published to rubygems to be consumed by the "public".

Personally, I'd like also to get a _1.0.0_ out as part of the CDK 2 final. To me it makes no sense to just increment micro counter and it definitely makes no sense to add yet another level.

Regarding the installer, a new release is required for the CDK either way. The final release of the CDK will need to include an updated version of the vagrant-service-manager gem. I believe the installer uses the gems bundled as part of the CDK zip. So in the end the installer should automatically get the right version of the gem.

Bottom line, afaik there is no consumable release for us atm.

> Docker connection does not work after cdk restart
> -------------------------------------------------
>
>                 Key: JBIDE-21947
>                 URL: https://issues.jboss.org/browse/JBIDE-21947
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdk, upstream
>    Affects Versions: 4.3.1.CR1
>            Reporter: Martin Malina
>            Assignee: Hardy Ferentschik
>             Fix For: 4.3.1.CR1
>
>
> When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work.
> This is caused by a bug in vagrant-service-manager 0.0.4:
> https://github.com/projectatomic/vagrant-service-manager/issues/80



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)