[
https://issues.jboss.org/browse/JBIDE-21947?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-21947:
---------------------------------------
[~rob.stryker], there is no such thing as 0.0.4.1. See the last comment on github:
{quote}
That's just added to differentiate it with older version (0.0.4).
Here, we are not adding yet another level. I have just created a gem which includes this
fix and given to Martin to testing since he was probably using the version which
didn't have fix.
{quote}
I believe this fix should be in 0.0.5 but I don't know when that's to be released.
Hopefully soon, so it can be included in cdk 2.0 and our installer.
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)