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

Roland Grunberg (JIRA) issues at jboss.org
Thu May 26 15:25:00 EDT 2016


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

Roland Grunberg commented on JBDS-3739:
---------------------------------------

I believe the issue with vagrant-service-manager is resolved. Stopping/starting the CDK VM any number of times doesn't fail any of the docker cli invocations. The last issue needing to be addressed on our end is that the CDK VM appears to update the certificates used or at least change something about them requiring us to re-create the connection. This is s something that will likely be addressed on the Eclipse Docker Tooling side as well. Xavier has a fix for this that we're reviewing.

> Docker connection does not work after cdk restart
> -------------------------------------------------
>
>                 Key: JBDS-3739
>                 URL: https://issues.jboss.org/browse/JBDS-3739
>             Project: Red Hat Developer Studio (DevStudio)
>          Issue Type: Bug
>          Components: cdk, platform-installer, upstream
>    Affects Versions: 9.1.0.CR1
>            Reporter: Martin Malina
>            Assignee: Marián Labuda
>            Priority: Blocker
>              Labels: havoc
>             Fix For: 10.0.0.Alpha3
>
>         Attachments: docker-frozen.txt
>
>
> 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)



More information about the jbosstools-issues mailing list