Problem to instantiate vagrant images

[geoHeil]

Hi,

Itry to run the openshift and kubernetes vagrant images. But both do not come up in the first place.

E.g. the kubernetese ones times out like:

[](
Could not initialise a client - is your server setting correct?
==> default:
==> default: couldn't read version from server: Get http://localhost:8080/api: dial tcp 127.0.0.1:8080: connection refused
==> default:
==> default: Waiting for the fabric8 console to start...
==> default: /tmp/vagrant-shell: line 74: kubectl: command not found
==> default: /tmp/vagrant-shell: line 74: kubectl: command not found
==> default: /tmp/vagrant-shell: line 74: kubectl: command not found)

[davsclaus]

Can you tell a bit more what you do? What vagrant image exactly are you using etc? Also you can get faster help on the IRC chat room.

We have the fabric8-install vagrant image here with fabric8 and OS3 together https://github.com/fabric8io/fabric8-installer/tree/master/vagrant/openshift

[geoHeil]

The error described is the error from yesterday. Today (after a fresh git clone) I get a bit further (see below) The problem described above still persists for the kubernetes (plain) vagrant image.

Following http://fabric8.io/guide/getStarted/vagrant.html I cloned $ git clone https://github.com/fabric8io/fabric8-installer.git and changed into the open shift folder.

A vagrant-up results in the following last messages:

==> default: --------------------------------------------------------------
==> default: Now open the fabric8 console at:
==> default:
==> default:     http://fabric8.vagrant.f8/
==> default:
==> default: Help on using the console:
==> default:
==> default:     http://fabric8.io/guide/getStarted/browserCertificates.html
==> default: --------------------------------------------------------------
==> default: deploymentconfig "docker-registry" created
==> default: service "docker-registry" created

checking out the URL http://fabric8.vagrant.f8/ I can see the console. No apps are installed

and the pods are running

oc get pods
NAME                                 READY     STATUS    RESTARTS   AGE
docker-registry-1-qzdvi              1/1       Running   0          2m
fabric8-4ts3b                        1/1       Running   0          4m
fluentd-elasticsearch-172.28.128.4   1/1       Running   0          2m
router-1-awl2k                       2/2       Running   0          2m

clicking on add app tells me to first run the CI CD pipeline which in turn tells me to run Accepting the next form with the default settings and clicking on run again presents me the following screen

Unfortunately, nothing seems to have happened. No new pods seem to be running