[JBoss JIRA] (JBIDE-23042) CDK server adapter: Can't launch latest CDK 2.2 in Windows 10
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23042?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-23042:
-----------------------------------
Fix Version/s: 4.4.1.Final
> CDK server adapter: Can't launch latest CDK 2.2 in Windows 10
> -------------------------------------------------------------
>
> Key: JBIDE-23042
> URL: https://issues.jboss.org/browse/JBIDE-23042
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Priority: Critical
> Labels: cdk
> Fix For: 4.4.1.Final
>
> Attachments: vagrant-output.txt
>
>
> When launching the latest CDK 2.2 candidate the following error occurrs:
> {code}
> [landrush] Using eth1 (172.28.128.3)
> [landrush] adding Landrush'es DNS server to network 'VirtualBox Host-Only Network #3' using DNS IP '172.28.128.3'' and search domain 'cdk'
> ==> default: The folowing SH comand responded with a non-zero exit status.
> ==> default: Vagrant asumes that this means the comand failed!
> ==> default: sudo rm /etc/docker/ca.pem & sudo systemctl restart docker
> ==> default: Stdout from the comand:
> ==> default: Stder from the comand:
> ==> default: rm: canot remove '/etc/docker/ca.pem': No such file or directory
> ==> default: Forcing shutdown of VM...
> ==> default: Destroying VM and associated drives...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> C:/Users/Administrator/.vagrant.d/gems/gems/vagrant-service-manager-1.4.0.dev/lib/vagrant-service-manager/services/docker.rb:20:in `execute': undefined method `zero?' for #<Thread:0x24a7250 dead> (NoMethodError)
> from C:/Users/Administrator/.vagrant.d/gems/gems/vagrant-service-manager-1.4.0.dev/lib/vagrant-service-manager/service.rb:20:in `each'
> {code}
> The complete vagrant output is here: [^vagrant-output.txt]
> See the following mail that Rob sent to the mailing list: http://post-office.corp.redhat.com/archives/devtools-program/2016-August/...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23042) CDK server adapter: Can't launch latest CDK 2.2 in Windows 10
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23042?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-23042:
-----------------------------------
Priority: Blocker (was: Critical)
> CDK server adapter: Can't launch latest CDK 2.2 in Windows 10
> -------------------------------------------------------------
>
> Key: JBIDE-23042
> URL: https://issues.jboss.org/browse/JBIDE-23042
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Priority: Blocker
> Labels: cdk
> Fix For: 4.4.1.Final
>
> Attachments: vagrant-output.txt
>
>
> When launching the latest CDK 2.2 candidate the following error occurrs:
> {code}
> [landrush] Using eth1 (172.28.128.3)
> [landrush] adding Landrush'es DNS server to network 'VirtualBox Host-Only Network #3' using DNS IP '172.28.128.3'' and search domain 'cdk'
> ==> default: The folowing SH comand responded with a non-zero exit status.
> ==> default: Vagrant asumes that this means the comand failed!
> ==> default: sudo rm /etc/docker/ca.pem & sudo systemctl restart docker
> ==> default: Stdout from the comand:
> ==> default: Stder from the comand:
> ==> default: rm: canot remove '/etc/docker/ca.pem': No such file or directory
> ==> default: Forcing shutdown of VM...
> ==> default: Destroying VM and associated drives...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> C:/Users/Administrator/.vagrant.d/gems/gems/vagrant-service-manager-1.4.0.dev/lib/vagrant-service-manager/services/docker.rb:20:in `execute': undefined method `zero?' for #<Thread:0x24a7250 dead> (NoMethodError)
> from C:/Users/Administrator/.vagrant.d/gems/gems/vagrant-service-manager-1.4.0.dev/lib/vagrant-service-manager/service.rb:20:in `each'
> {code}
> The complete vagrant output is here: [^vagrant-output.txt]
> See the following mail that Rob sent to the mailing list: http://post-office.corp.redhat.com/archives/devtools-program/2016-August/...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23042) CDK server adapter: Can't launch latest CDK 2.2 in Windows 10
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23042?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-23042:
-----------------------------------
Component/s: cdk
upstream
(was: openshift)
> CDK server adapter: Can't launch latest CDK 2.2 in Windows 10
> -------------------------------------------------------------
>
> Key: JBIDE-23042
> URL: https://issues.jboss.org/browse/JBIDE-23042
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Priority: Blocker
> Labels: cdk
> Fix For: 4.4.1.Final
>
> Attachments: vagrant-output.txt
>
>
> When launching the latest CDK 2.2 candidate the following error occurrs:
> {code}
> [landrush] Using eth1 (172.28.128.3)
> [landrush] adding Landrush'es DNS server to network 'VirtualBox Host-Only Network #3' using DNS IP '172.28.128.3'' and search domain 'cdk'
> ==> default: The folowing SH comand responded with a non-zero exit status.
> ==> default: Vagrant asumes that this means the comand failed!
> ==> default: sudo rm /etc/docker/ca.pem & sudo systemctl restart docker
> ==> default: Stdout from the comand:
> ==> default: Stder from the comand:
> ==> default: rm: canot remove '/etc/docker/ca.pem': No such file or directory
> ==> default: Forcing shutdown of VM...
> ==> default: Destroying VM and associated drives...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> C:/Users/Administrator/.vagrant.d/gems/gems/vagrant-service-manager-1.4.0.dev/lib/vagrant-service-manager/services/docker.rb:20:in `execute': undefined method `zero?' for #<Thread:0x24a7250 dead> (NoMethodError)
> from C:/Users/Administrator/.vagrant.d/gems/gems/vagrant-service-manager-1.4.0.dev/lib/vagrant-service-manager/service.rb:20:in `each'
> {code}
> The complete vagrant output is here: [^vagrant-output.txt]
> See the following mail that Rob sent to the mailing list: http://post-office.corp.redhat.com/archives/devtools-program/2016-August/...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23042) CDK server adapter: Can't launch latest CDK 2.2 in Windows 10
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23042?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-23042:
--------------------------------------
Assignee: Rob Stryker
> CDK server adapter: Can't launch latest CDK 2.2 in Windows 10
> -------------------------------------------------------------
>
> Key: JBIDE-23042
> URL: https://issues.jboss.org/browse/JBIDE-23042
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: cdk
> Fix For: 4.4.1.Final
>
> Attachments: vagrant-output.txt
>
>
> When launching the latest CDK 2.2 candidate the following error occurrs:
> {code}
> [landrush] Using eth1 (172.28.128.3)
> [landrush] adding Landrush'es DNS server to network 'VirtualBox Host-Only Network #3' using DNS IP '172.28.128.3'' and search domain 'cdk'
> ==> default: The folowing SH comand responded with a non-zero exit status.
> ==> default: Vagrant asumes that this means the comand failed!
> ==> default: sudo rm /etc/docker/ca.pem & sudo systemctl restart docker
> ==> default: Stdout from the comand:
> ==> default: Stder from the comand:
> ==> default: rm: canot remove '/etc/docker/ca.pem': No such file or directory
> ==> default: Forcing shutdown of VM...
> ==> default: Destroying VM and associated drives...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> C:/Users/Administrator/.vagrant.d/gems/gems/vagrant-service-manager-1.4.0.dev/lib/vagrant-service-manager/services/docker.rb:20:in `execute': undefined method `zero?' for #<Thread:0x24a7250 dead> (NoMethodError)
> from C:/Users/Administrator/.vagrant.d/gems/gems/vagrant-service-manager-1.4.0.dev/lib/vagrant-service-manager/service.rb:20:in `each'
> {code}
> The complete vagrant output is here: [^vagrant-output.txt]
> See the following mail that Rob sent to the mailing list: http://post-office.corp.redhat.com/archives/devtools-program/2016-August/...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23042) CDK server adapter: Can't launch latest CDK 2.2 in Windows 10
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23042?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23042:
------------------------------------------
CC: [~rob.stryker]
> CDK server adapter: Can't launch latest CDK 2.2 in Windows 10
> -------------------------------------------------------------
>
> Key: JBIDE-23042
> URL: https://issues.jboss.org/browse/JBIDE-23042
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Priority: Critical
> Labels: cdk
> Attachments: vagrant-output.txt
>
>
> When launching the latest CDK 2.2 candidate the following error occurrs:
> {code}
> [landrush] Using eth1 (172.28.128.3)
> [landrush] adding Landrush'es DNS server to network 'VirtualBox Host-Only Network #3' using DNS IP '172.28.128.3'' and search domain 'cdk'
> ==> default: The folowing SH comand responded with a non-zero exit status.
> ==> default: Vagrant asumes that this means the comand failed!
> ==> default: sudo rm /etc/docker/ca.pem & sudo systemctl restart docker
> ==> default: Stdout from the comand:
> ==> default: Stder from the comand:
> ==> default: rm: canot remove '/etc/docker/ca.pem': No such file or directory
> ==> default: Forcing shutdown of VM...
> ==> default: Destroying VM and associated drives...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> C:/Users/Administrator/.vagrant.d/gems/gems/vagrant-service-manager-1.4.0.dev/lib/vagrant-service-manager/services/docker.rb:20:in `execute': undefined method `zero?' for #<Thread:0x24a7250 dead> (NoMethodError)
> from C:/Users/Administrator/.vagrant.d/gems/gems/vagrant-service-manager-1.4.0.dev/lib/vagrant-service-manager/service.rb:20:in `each'
> {code}
> The complete vagrant output is here: [^vagrant-output.txt]
> See the following mail that Rob sent to the mailing list: http://post-office.corp.redhat.com/archives/devtools-program/2016-August/...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23043) Not working connection to CDK Docker deamon
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23043?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23043:
------------------------------------------
This also prevents openshift from deploying images to the docker registry that runs in OpenShift: JBIDE-23031
> Not working connection to CDK Docker deamon
> -------------------------------------------
>
> Key: JBIDE-23043
> URL: https://issues.jboss.org/browse/JBIDE-23043
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, docker
> Affects Versions: 4.4.1.Final
> Environment: F24,
> Devstudio:
> Version: 10.1.0.GA
> Build id: GA-v20160825-0621-B5857
> Build date: 20160825-0621
> Docker Tooling:
> 2.1.0.20160825102
> Reporter: Josef Kopriva
>
> After upgrading Docker Tooling to latest nightly, I cannot create connection to the Docker CDK deamon through TCP connection with certificates.
> Stacktrace:
> {code:java}
> An internal error occurred during: "Opening connection...".
> java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMParser
> at com.spotify.docker.client.DockerCertificates.<init>(DockerCertificates.java:80)
> at com.spotify.docker.client.DockerCertificates.<init>(DockerCertificates.java:64)
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:83)
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:47)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:252)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$1.run(DockerExplorerContentProvider.java:179)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23043) Not working connection to CDK Docker deamon
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23043?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23043:
-------------------------------------
Component/s: openshift
> Not working connection to CDK Docker deamon
> -------------------------------------------
>
> Key: JBIDE-23043
> URL: https://issues.jboss.org/browse/JBIDE-23043
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, docker, openshift
> Affects Versions: 4.4.1.Final
> Environment: F24,
> Devstudio:
> Version: 10.1.0.GA
> Build id: GA-v20160825-0621-B5857
> Build date: 20160825-0621
> Docker Tooling:
> 2.1.0.20160825102
> Reporter: Josef Kopriva
>
> After upgrading Docker Tooling to latest nightly, I cannot create connection to the Docker CDK deamon through TCP connection with certificates.
> Stacktrace:
> {code:java}
> An internal error occurred during: "Opening connection...".
> java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMParser
> at com.spotify.docker.client.DockerCertificates.<init>(DockerCertificates.java:80)
> at com.spotify.docker.client.DockerCertificates.<init>(DockerCertificates.java:64)
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:83)
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:47)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:252)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$1.run(DockerExplorerContentProvider.java:179)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23043) Not working connection to CDK Docker deamon
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23043?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23043:
-------------------------------------
Component/s: (was: openshift)
> Not working connection to CDK Docker deamon
> -------------------------------------------
>
> Key: JBIDE-23043
> URL: https://issues.jboss.org/browse/JBIDE-23043
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, docker
> Affects Versions: 4.4.1.Final
> Environment: F24,
> Devstudio:
> Version: 10.1.0.GA
> Build id: GA-v20160825-0621-B5857
> Build date: 20160825-0621
> Docker Tooling:
> 2.1.0.20160825102
> Reporter: Josef Kopriva
>
> After upgrading Docker Tooling to latest nightly, I cannot create connection to the Docker CDK deamon through TCP connection with certificates.
> Stacktrace:
> {code:java}
> An internal error occurred during: "Opening connection...".
> java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMParser
> at com.spotify.docker.client.DockerCertificates.<init>(DockerCertificates.java:80)
> at com.spotify.docker.client.DockerCertificates.<init>(DockerCertificates.java:64)
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:83)
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:47)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:252)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$1.run(DockerExplorerContentProvider.java:179)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23043) Not working connection to CDK Docker deamon
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23043?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-23043:
---------------------------------------
[~nickboldt], do you have any idea what could be wrong here ?
> Not working connection to CDK Docker deamon
> -------------------------------------------
>
> Key: JBIDE-23043
> URL: https://issues.jboss.org/browse/JBIDE-23043
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, docker
> Affects Versions: 4.4.1.Final
> Environment: F24,
> Devstudio:
> Version: 10.1.0.GA
> Build id: GA-v20160825-0621-B5857
> Build date: 20160825-0621
> Docker Tooling:
> 2.1.0.20160825102
> Reporter: Josef Kopriva
>
> After upgrading Docker Tooling to latest nightly, I cannot create connection to the Docker CDK deamon through TCP connection with certificates.
> Stacktrace:
> {code:java}
> An internal error occurred during: "Opening connection...".
> java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMParser
> at com.spotify.docker.client.DockerCertificates.<init>(DockerCertificates.java:80)
> at com.spotify.docker.client.DockerCertificates.<init>(DockerCertificates.java:64)
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:83)
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:47)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:252)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$1.run(DockerExplorerContentProvider.java:179)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23043) Not working connection to CDK Docker deamon
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23043?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-23043:
---------------------------------------
The {{com.spotify.docker.client}} bundle that is required by the {{org.eclipse.linuxtools.docker.core}} includes a dependency on {{org.bouncycastle.openssl}}:
{code}
Manifest-Version: 1.0
Bundle-SymbolicName: com.spotify.docker.client
Archiver-Version: Plexus Archiver
Built-By: rgrunberg
Require-Bundle: org.glassfish.hk2.locator;bundle-version="2.3.0"
Bundle-ManifestVersion: 2
Bundle-Vendor: %bundleVendor
Import-Package: com.fasterxml.jackson.annotation;version="[2.2,3)",com
.fasterxml.jackson.core;version="[2.2,3)",com.fasterxml.jackson.datab
ind,com.fasterxml.jackson.databind.module,com.fasterxml.jackson.datab
ind.node,com.fasterxml.jackson.databind.util,com.fasterxml.jackson.da
tatype.guava,com.google.common.base;version="[15.0,18)",com.google.co
mmon.collect;version="[15.0,18)",com.google.common.io;version="[15.0,
18)",com.google.common.net;version="[15.0,18)",javax.net.ssl,javax.ws
.rs;version="[2.0,3)",javax.ws.rs.client;version="[2.0,3)",javax.ws.r
s.core;version="[2.0,3)",javax.ws.rs.ext;version="[2.0,3)",jnr.unixso
cket,org.apache.commons.compress.archivers;version="[1.6,2)",org.apac
he.commons.compress.archivers.tar;version="[1.6,2)",org.apache.common
s.compress.compressors.gzip;version="[1.6,2)",org.apache.http,org.apa
che.http.client.config,org.apache.http.config,org.apache.http.conn,or
g.apache.http.conn.socket,org.apache.http.conn.ssl,org.apache.http.im
pl.conn,org.apache.http.protocol,org.bouncycastle.asn1.pkcs;version="
[1.51,2)",org.bouncycastle.openssl;version="[1.51,2)",org.glassfish.h
k2.api;version="[2.3,3)",org.glassfish.jersey.apache.connector,org.gl
assfish.jersey.client;version="[2.13,3)",org.glassfish.jersey.client.
spi;version="[2.13,3)",org.glassfish.jersey.internal.util;version="[2
.13,3)",org.glassfish.jersey.jackson;version="[2.13,3)",org.slf4j;ver
sion="[1.7,2)"
{code}
Besides, there as been no upgrade of the {{com.spotify.docker.client}} bundle for a while.
What's really weird is that the action of updating the Docker Tooling seems to disable/remove the BouncyCastler from the TP.
> Not working connection to CDK Docker deamon
> -------------------------------------------
>
> Key: JBIDE-23043
> URL: https://issues.jboss.org/browse/JBIDE-23043
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, docker
> Affects Versions: 4.4.1.Final
> Environment: F24,
> Devstudio:
> Version: 10.1.0.GA
> Build id: GA-v20160825-0621-B5857
> Build date: 20160825-0621
> Docker Tooling:
> 2.1.0.20160825102
> Reporter: Josef Kopriva
>
> After upgrading Docker Tooling to latest nightly, I cannot create connection to the Docker CDK deamon through TCP connection with certificates.
> Stacktrace:
> {code:java}
> An internal error occurred during: "Opening connection...".
> java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMParser
> at com.spotify.docker.client.DockerCertificates.<init>(DockerCertificates.java:80)
> at com.spotify.docker.client.DockerCertificates.<init>(DockerCertificates.java:64)
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:83)
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:47)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:252)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$1.run(DockerExplorerContentProvider.java:179)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months