[JBoss JIRA] (JBIDE-23043) Not working connection to CDK Docker deamon
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23043?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-23043:
----------------------------------
Steps to Reproduce:
1. Install nightly build of devstudio
2. Install latest Docker Tooling from update site
3. Run CDK
4. Try to create new connection in Docker Explorer to connect to Docker CDK deamon
5. Connection is created(without Test Connection), but error is shown in error log
was:
1. Install nightly build of devstudio
2. Install latest Docker Tooling from update site
3. Run CDK
4. Try to create new connection in Docker Explorer to connect to Docker CDK deamon
5. Connection is created(without ping), but error is shown in error log
> 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 Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23043?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-23043:
----------------------------------
Steps to Reproduce:
1. Install nightly build of devstudio
2. Install latest Docker Tooling from update site
3. Run CDK
4. Try to create new connection in Docker Explorer to connect to Docker CDK deamon
5. Connection is created(without ping), but error is shown in error log
was:
1. Install nightly build of devstudio
2. Install latest Docker Tooling from update site
3. Run CDK
4. Try to create new connection in Docker Explorer to connect to Docker CDK deamon
> 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 Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23043?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-23043:
----------------------------------
Summary: Not working connection to CDK Docker deamon (was: Not working connection to CDK Docker Repository)
> 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 Repository
by Josef Kopriva (JIRA)
Josef Kopriva created JBIDE-23043:
-------------------------------------
Summary: Not working connection to CDK Docker Repository
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-23042) CDK server adapter: Cant 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 updated JBIDE-23042:
-------------------------------------
Summary: CDK server adapter: Cant launch latest CDK 2.2 in Windows 10 (was: CDK server adapter: Cant launch latest CDK 2.2 in Wondows 10)
> CDK server adapter: Cant 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-23042) CDK server adapter: Can't launch latest CDK 2.2 in Windows 10
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23042?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-23042:
----------------------------------
Summary: CDK server adapter: Can't launch latest CDK 2.2 in Windows 10 (was: CDK server adapter: Cant launch latest CDK 2.2 in Windows 10)
> 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-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 updated JBIDE-23042:
-------------------------------------
Labels: cdk (was: )
> 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-23042) CDK server adapter: Cant launch latest CDK 2.2 in Wondows 10
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23042?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23042:
-------------------------------------
Priority: Critical (was: Major)
> CDK server adapter: Cant launch latest CDK 2.2 in Wondows 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
> 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: Cant launch latest CDK 2.2 in Wondows 10
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23042?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23042:
-------------------------------------
Attachment: vagrant-output.txt
> CDK server adapter: Cant launch latest CDK 2.2 in Wondows 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
> 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: Cant launch latest CDK 2.2 in Wondows 10
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-23042:
----------------------------------------
Summary: CDK server adapter: Cant launch latest CDK 2.2 in Wondows 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
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