Public | Automated Build

Last pushed: never
Short Description
HashiCorp Vault
Full Description

Docker Vault

This Docker Vault container is using Busybox and Hashicorp's Vault.

Vault uses TCP/8200 by default, so we'll keep that. The demo configuration is listening on all interfaces (not just localhost), and using demo.consul.io as per the getting started docs.

Configuration is stored under config/.

The automated latest build is always available at containersol/vault:

$ docker pull containersol/vault

Vault Server

As per Issue 59, need to add --cap-add IPC_LOCK option.

Start by default in dev mode:

$ docker run -t -i \
  --cap-add IPC_LOCK \
  -p 8200:8200 \
  --hostname vault \
  --name vault containersol/vault

Start with a demo Consul backend using demo.consul.io:

$ docker run -t -i \
  --cap-add IPC_LOCK \
  -p 8200:8200 \
  --hostname vault \
  --name vault \
  --volume $PWD/config:/config \
  containersol/vault -config=/config/demo.hcl

If you have a running Consul container named consul, you can just use it:

$ docker run -t -i \
  --cap-add IPC_LOCK \
  -p 8200:8200 \
  --hostname vault \
  --name vault \
  --link consul:consul \
  --volume $PWD/config:/config \
  containersol/vault -config=/config/consul.hcl

To initialize Vault, on your workstation with vault installed:

$ export VAULT_ADDR='http://a.b.c.d:8200'
$ vault init

Then RTFM for Vault usage.

Consul

I'm using Progrium's Consul Docker box, it's working great.
Here's with the WebUI:

$ docker run -p 8400:8400 -p 8500:8500 -p 8600:53/udp --hostname consul --name consul progrium/consul -server -bootstrap -ui-dir /ui

The WebGUI should be available.

Docker Pull Command
Owner
containersol
Source Repository

Comments (0)