[
https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin....
]
Alexey Kazakov commented on JBDS-3739:
--------------------------------------
[~rgrunber] could you please add a link to the bugzilla issue for that docker tooling
bug?
And please open an issue for vagrant-service-manager here -
https://github.com/projectatomic/vagrant-service-manager
It's very important that we don't quietly wait until the issue is fixed somehow.
Report it upstream or ping CDK guys if not sure it's an upstream bug or not.
There is a free node channel #nulecule where you can ask the ADB/CDK guys.
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)