[jbosstools-issues] [JBoss JIRA] (JBIDE-23042) CDK server adapter: Can't launch latest CDK 2.2 in Windows 10

[Xavier Coulon (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-23042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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/msg00114.html



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)