Member preview

Running Vault for Development

This is only for development or experimentation.

Hashicorp Vault secures, stores, and tightly controls access to tokens, passwords, certificates, API keys, and other secrets in modern computing.

Using the Container

$ docker run -it -p 8200:8200 --name=dev-vault vault:1.0.0-beta1
Unable to find image 'vault:1.0.0-beta1' locally
1.0.0-beta1: Pulling from library/vault
4fe2ade4980c: Already exists
b48f6305d47f: Pull complete
dfd03e9a3806: Pull complete
ce46f1b4b399: Pull complete
2a46728a739d: Pull complete
Digest: sha256:cb99fb9f501cfcf785e69c977c9fa85575e0bad51614965d80c5582
Status: Downloaded newer image for vault:1.0.0-beta1
==> Vault server configuration:
Api Address: http://0.0.0.0:8200
Cgo: disabled
Cluster Address: https://0.0.0.0:8201
Log Level: (not set)
Mlock: supported: true, enabled: false
Storage: inmem
Version: Vault v1.0.0-beta1
Version Sha: ebc733f4ca5d362fdfb302ac75953228585c54a2
WARNING! dev mode is enabled! In this mode, Vault runs entirely in-memory and starts unsealed with a single unseal key. The root token is already authenticated to the CLI, so you can immediately begin using Vault.
You may need to set the following environment variable:
$ export VAULT_ADDR='http://0.0.0.0:8200'
The unseal key and root token are displayed below in case you want to
seal/unseal the Vault or re-authenticate.
Unseal Key: EMaMwqvkwRfYwNYwa+SZ42+k56JE0lRgAaRD000c17A=
Root Token: s.8lY29qXRGtQgFioaLPrQAwMl
Development mode should NOT be used in production installations!
==> Vault server started! Log data will stream in below:

Vault UI

Launch the Vault UI by entering <V http://localhost:8200/ui in the web browser.

Enter the root token and click Sign In.

OS: macOS Mojaveh version 10.14 (18A391)
Docker Client: 18.06.1-ce, build e68fc7a
Docker Engine: 18.06.1-ce-mac73 (26764)