EXAMPLES: vagrant + CoreOS for dev workspaces

The base vagrant / CoreOS parts of this repo are shamelessly ripped from the CoreOS-vagrant repo

Why?

Working with applications running on CoreOS, it can be useful to run your own local instance for emulating issues or developing automation for it.

Customised homedir assets / login config

This variation of the official repo lets you configure the core user's home dir as you'd like. So you can drop your own .aws dir, .ssh, .gitconfig or profile.d scripts without mounting from your host to theh VM.

It will also handle files in the homedir with Windows line-endings correctly.

devbox workspaces

There is a shell helper function devbox as part of the deployed .bashrc. This drops the user in to a docker container with user-defined volumes mapped from the CoreOS host.

See the devbox_aws and my derived devbox_aws_coreos containers for more information.

I use the latter to develop automation for dockerised apps on AWS - running on CoreOS instances, naturally ;)

However the default opsgang/devbox_aws:stable image used by the devbox function is os-agnostic.

shell functions (.bashrc)

• forwardSsh(): creates an ssh-agent (or will re-use an existing one) adding all of the keys under the core user's .ssh dir.

• devbox(): drops the user in to a new named container, or in to an existing one of the same name. You can export the following 2 vars to your env before calling devbox()

  • $DEFAULT_DEVBOX_IMAGE defaults to opsgang/devbox_aws - set this to your own custom one as desired.

  • $DEFAULT_DEVBOX_USER defaults to root - set this to the user appropriate for your DEVBOX_IMAGE