History

Justin Santa Barbara 5a056a3872 Bump all our base docker images		2017-11-28 02:41:03 -05:00
..
Dockerfile	Bump all our base docker images	2017-11-28 02:41:03 -05:00
Dockerfile-light	Bump all our base docker images	2017-11-28 02:41:03 -05:00
README.md	Dockerfile for kops	2017-04-23 14:16:11 -05:00

README.md

Running Kops in Docker

The Dockerfile here is offered primarily as a way to build continuous integration versions of kops until we figure out how we want to release/package it.

To use it, e.g. (assumes your $HOME is correct and that $KOPS_STATE_STORE is correct):

$ docker build -t kops .
$ KOPS="docker run -v $HOME/.aws:/root/.aws:ro -v $HOME/.ssh:/root/.ssh:ro -v $HOME/.kube:/root/.kube -it kops --state=$KOPS_STATE_STORE"

This creates a shell variable that runs the kops container with ~/.aws mounted in (for AWS credentials), ~/.ssh mounted in (for SSH keys, for AWS specifically), and ~/.kube mounted in (so kubectl can add newly created clusters).

After this, you can just use $KOPS where you would generally use kops, e.g. $KOPS get cluster.

Choose branch/release to build.

By default, the current release branch is built. To build using a specific tag or commit, add the flag --build-arg KOPS_GITISH=<tag/branch/sha> to docker build, e.g. docker build --build-arg KOPS_GITISH=release-1.6 -t kops .

Light Version

The light version downloads the latest release binaries of kops from Github Releases.

To build the lighter version:

$ docker build -t kops:light -f Dockerfile-light .
$ KOPS="docker run -v $HOME/.aws:/root/.aws:ro -v $HOME/.ssh:/root/.ssh:ro -v $HOME/.kube:/root/.kube -it kops:light --state=$KOPS_STATE_STORE"