History

Zach Loafman 9bf3ab5617 Docker build: Fix models After playing with the pulled Docker container again, we need to make sure the models are really alongside the executed binary (kops doesn't resolve the symlink). Simplify this a bit, too.		2016-08-17 11:38:54 -07:00
..
Dockerfile	Docker build: Fix models	2016-08-17 11:38:54 -07:00
README.md	CI: Add container build	2016-08-15 17:08:11 -07:00
build-squash-push.sh	Build: Refine slightly how the tag is cleaned	2016-08-17 11:04:46 -07: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 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.