This page describes how to setup your local development machine or host to work with Kubernetes or OpenShift either remotely or via fabric8 vagrant image.
openshift, oc and osadm executables to your PATHoc login --server=https://172.28.128.4:8443
You should now be able to use the oc CLI tool to work with Kubernetes and OpenShift resources:
oc get pods
The following environment variables are useful. The following are for the fabric8 vagrant image; if you are running on a different box just update the IP / domain names:
export KUBERNETES_MASTER=https://172.28.128.4:8443
export KUBERNETES_DOMAIN=vagrant.f8
export KUBERNETES_NAMESPACE=default
This step is optional but if you are running the fabric8 vagrant image and don't have a wildcard DNS entry setup for *.vagrant.f8 then you might want to add an entry in your /etc/hosts file so that you can access services via their routes.
172.28.128.4 vagrant.f8 fabric8.vagrant.f8 fabric8-master.vagrant.f8 docker-registry.vagrant.f8 gogs.vagrant.f8 nexus.vagrant.f8 jenkins.vagrant.f8
Where 172.28.128.4 is the IP address of your OpenShift master (which it is for the fabric8 vagrant image)
e.g. if you Install Fabric8 on OpenShift then you should be able to access the console at http://fabric8.vagrant.f8/
If you are using a vagrant image such as the Fabric8 vagrant image then you should setup your host to reuse the same docker daemon that is inside the vagrant image; this lets you develop locally without having to push or pull images to or from a docker registry which greatly speeds up local development.
So set this environment variable:
export DOCKER_HOST=tcp://vagrant.f8:2375
And don't define any of the other docker env vars like DOCKER_CERT_PATH or DOCKER_TLS_VERIFY.
Now when in a shell on your host (OS X / Windows) you can type docker ps and the output is the same as if you type the same command inside the vagrant ssh shell inside the vagrant VM.
This then means that your host (OS X / Windows) will use the same docker daemon as the Kubernetes running inside the fabric8 vagrant image. Because of this you don't need to use a docker registry; a docker daemon is kinda like a local registry anyway - provided you don't try to push or pull the image!
NOTE you need to make sure that your kubernetes JSON uses the imagePullPolicy of PullIfAbsent (via the maven property fabric8.imagePullPolicy); as any attempt to pull an image just built locally that isn't pushed to a docker registry won't work; since the image isn't public yet. In fabric8 2.2.3 the default in mvn fabric8:json is to now omit this value which means it uses the kubernetes default which is PullIfAbsent.
You now should be able to build and use docker images locally without pushing or pulling.