[
https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin....
]
Martin Malina commented on JBDS-3739:
-------------------------------------
I can confirm that it doesn't work for me either.
When I start JBDS 10.0.0.Alpha2, set up cdk and start it for the first time (clean
workspace), it works. Then I stop it, start again.
This time the docker connection in docker explorer was grey/inactive and the cdk adapter
was stuck on Starting. And eventually my jbds froze and kept exhausting my cpu.
Then I killed it and repeated with a new workspace. This time I got exactly the same
result as Marian - on second start of cdk, Docker connection didn't work and I got
this error:
{code}
Error contacting OpenShift
The CDK VM is up and running, but OpenShift is unreachable at url
https://10.1.2.2:8443/healthz/ready
{code}
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.x
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)