[
https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin....
]
Roland Grunberg commented on JBDS-3739:
---------------------------------------
There's a few issues at hand, one of which has apparently been fixed in a later
version vagrant-service-manager.
First, when one restarts a cdk vagrant VM, the certificates aren't copied over
properly and so any attempt to connect to the daemon will fail. On top of this issue, it
was also discovered that the Eclipse Docker Tooling (or some combination of it and other
plugins) causes a UI freeze on OSX when the vagrant-service-manager issue occurs. I'm
able to reproduce the freeze on Linux although the UI eventually recovers, but likely the
same issue.
I have an idea of what the issue might be and just need to test it out to confirm it
works, or continue investigating if not.
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)