[jbosstools-issues] [JBoss JIRA] (JBIDE-23009) Cannot connect to cdk docker in Docker Explorer
Martin Malina (JIRA)
issues at jboss.org
Tue Aug 16 10:49:01 EDT 2016
[ https://issues.jboss.org/browse/JBIDE-23009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279778#comment-13279778 ]
Martin Malina edited comment on JBIDE-23009 at 8/16/16 10:48 AM:
-----------------------------------------------------------------
CDK 2.1 still works fine. So this should not really block AM3 release. The issue is only reproducible with CDK 2.2 rc1 atm.
was (Author: mmalina):
CDK 2.1 still works fine. So this should really block AM3 release. The issue is only reproducible with CDK 2.2 rc1 atm.
> Cannot connect to cdk docker in Docker Explorer
> -----------------------------------------------
>
> Key: JBIDE-23009
> URL: https://issues.jboss.org/browse/JBIDE-23009
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Xavier Coulon
> Priority: Critical
>
> When I start CDK 2.2, docker connection is correctly created, but it cannot connect. There is no error message anywhere.
> If I try to create a connection manually, using details from "vagrant service-manager env", the ping fails and it doesn't work either.
> Connection from CLI, on the other hand, to this docker daemon works fine - when I run the export commands:
> {code}
> export DOCKER_HOST=tcp://172.28.128.3:2376
> export DOCKER_CERT_PATH=/Users/rasp/jbossqa/cdk2.2.rc1/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
> export DOCKER_TLS_VERIFY=1
> export DOCKER_API_VERSION=1.22
> {code}
> and then try for example "docker ps" or "docker run hello-world".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list