[
https://issues.jboss.org/browse/JBIDE-23009?page=com.atlassian.jira.plugi...
]
Xavier Coulon commented on JBIDE-23009:
---------------------------------------
Hello [~mmalina],
As I explained above, the Docker daemon in CDK 2.2 returns a response that contains the
list of containers in a JSON format, but the 'content' header is {{text/plain}}
instead of {{application/json}} and thus, the Docker client does not know how to
handle/deserialize the response message.
We should see if this problem occurs in the latest 2.2 build and raise the issue upstream
(CDK team) if it is the case.
Cannot connect to cdk 2.2 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)