Important: Jube 2.x does not work currently. We are aware of issues with Jube 2.x due recent Kubernetes schema updates and ongoing migration of using the same hawtio web console for Jube and OpenShift/Docker.
First you need to get the latest Jube by downloading jube-2.2.3-image.zip and unzipping it:
curl -O http://central.maven.org/maven2/io/fabric8/jube/images/jube/jube/2.2.3/jube-2.2.3-image.zip
mkdir jube-2.2.3-image
cd jube-2.2.3-image
unzip ../jube-2.2.3-image.zip
You can then startup Jube via:
./run.sh
If your operating system doesn't have the executable flag set on the run script; try
chmod +x *.sh *.bat bin/*
To stop Jube hit Ctrl-C.
If you want to run Jube in the background you can run ./start.sh then you can run ./stop.sh to stop it or run ./status.sh to see if its still running.
The following environment variables are used by various Tools such as the Console, Maven Plugin, the Forge Addons and the java libraries:
export KUBERNETES_MASTER=http://localhost:8585/
export FABRIC8_CONSOLE=http://localhost:8585/hawtio/
Once you have set those in your shell (or ~/.bashrc) you can then use all the fabric8 tools against your local Jube node.
Once Jube has started up you should be able to open the Console at http://localhost:8585/hawtio/ to view the kubernetes system. You can then view these tabs:
Jube implements the Kubernetes REST API so you can use any kubernetes tools with Jube such as the Console or Forge Addons to work with pods, replication controllers or services - provided that any docker images referenced in the pods and pod templates have a suitable image zip. For more detail on this see the Jube Goals details on Jube Image Zips and check out the differences between Jube and Kubernetes
If maven builds fail it may be you have not setup the environment variables correctly; see above.
Otherwise check out the Jube Troubleshooting Guide for details of how to check the logs and web console.