-
There are fabric8-snapshot profiles all over that set fabric8.version to 2.3-SNAPSHOT, which should be removed.
-
I am installing the ipaas app on latest release and did a `oc get pods --watch` and noticed it printed
api-registry-bwhtn 0/1 Error pulling image (2.2.1) from docker.io/fabric8/api-registry, …
-
In the quickstarts that uses a java main class, we should put that as a property with a known key. This makes forge tooling easier, and also for users as they can spot the main class as a property. An…
-
On page http://fabric8.io/guide/getStarted/vagrant.html, link to download fabric8 templates 2.2.33 distribution doesn't work. File not found.
-
or something.
```
davsclaus:~/workspace/fabric8-installer/vagrant/openshift (master)/$ oc logs quickstart-java-simple-fatjar-huuyn
I> No access restrictor found, access to all MBean is allowed
Joloki…
-
Just tried the latest fabric8 vagrant image and get:
Error response from daemon: client and server don't have same version (client : 1.19, server: 1.18)
I have just upgraded to the latest version of…
-
Version used : 2.2.240
There is still an issue when I try to access the hawt/jolokia console of a container
```
[15:33:27] A 503 indicates more an error of the API proxy then on the Jolokia side.…
-
I upgraded to 1.7.0 with latest boot2docker, and followed the install guide, and noticed the pods was not ready - they were in `pending` state.
And `docker ps` reported version miss-match as my clien…
-
then folks can just open the web console (when its up).
Also I wonder if we should install a few of the common OpenShift templates (e.g. management / logging / metrics / cdelivery-core / cdelivery / …
-
in the karaf camel-log it fails with some error. Just logged a ticket to not forget