[
https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin....
]
Martin Malina edited comment on JBDS-3739 at 4/8/16 4:44 AM:
-------------------------------------------------------------
[~rob.stryker], I don't know when the next build of cdk.zip is available, but
vagrant-service-manager 1.0.0 has been released and is available using: vagrant plugin
install vagrant-service-manager
This should be the final version for our release if no major issues are found. Or so says
Hardy :)
EDIT: It turns out there is a new build of CDK right now. It's a candidate for GA.
http://cdk-builds.usersys.redhat.com/builds/weekly/08-Apr-2016/
was (Author: mmalina):
[~rob.stryker], I don't know when the next build of cdk.zip is available, but
vagrant-service-manager 1.0.0 has been released and is available using: vagrant plugin
install vagrant-service-manager
This should be the final version for our release if no major issues are found. Or so says
Hardy :)
Docker connection does not work after cdk restart
-------------------------------------------------
Key: JBDS-3739
URL:
https://issues.jboss.org/browse/JBDS-3739
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: cdk, installer, upstream
Affects Versions: 9.1.0.CR1
Reporter: Martin Malina
Assignee: Hardy Ferentschik
Priority: Blocker
Labels: havoc
Fix For: 9.1.0.GA
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)