Last modified January 2, 2017

Running a Private Docker Registry

If you want to store truly private Docker images for your cluster, you might want to run your own private Docker registry inside of it.

Keep in mind that this recipe currently does not include SSL or authentification. To work around this, there’s a proxy running on each node in the cluster, exposing a port onto the node (via hostPort), which Docker accepts as “secure”, since it is accessed via localhost.

Note: The registry set up by this recipe currently uses non-persistent storage, so images pushed to it will not survive Pod restarts.

Deploying the registry

To deploy the registry just apply the manifests included in this recipe.

kubectl apply --filename

Using the registry

First, to push images to your private registry from the outside you can set up port forwarding with kubectl.

$ REGISTRY_POD_NAME=$(kubectl get pods --namespace registry -l app=registry,component=main \
  -o template --template '{{(index .items 0)}}')

$ kubectl --namespace registry port-forward $REGISTRY_POD_NAME 5000:5000

Note: This only works if you run kucectl and docker on the same host, like in Linux. On Mac or Windows, Docker usually runs inside a VM, so you would need to install, configure, and run the above kubectl command inside that VM.

You can then use your local docker client to push images to localhost:5000.

$ docker pull alpine
$ docker tag alpine localhost:5000/user/container:tag
$ docker push localhost:5000/user/container:tag

To use this image in your Pods, you need to specify it in your Pod’s spec.containers[].image field:

image: localhost:5000/user/container:tag

\n You can collaborate on this recipe on GitHub.