This is a Dockerized image of Hashicorp's Vault. Vault is tool to securely access secrets such as API keys, passwords, certificates, token, and so on.
A pre-built image is available on Docker Hub and can be run as follows:
docker run -it cgswong/vault:latest
By default the container will run the vault command showing the version. Simply run your regular vault commands as normal to use the image.
vault binds to 127.0.0.1 by default, make sure you bind vault's listener to to 0.0.0.0.
when running the development server, vault binds to localhost by default. A possible workaround would be to create the following vault config:
listener "tcp" {
address = "0.0.0.0:9000"
tls_disable = 1
}
and then pass the configuration to vault. for example, if you saved the mentioned configuration at /tmp/vault.conf:
docker run -it --expose 9000 -p 127.0.0.1:8200:9000 \
-v /tmp/vault.conf:/root/vault.conf cgswong/vault:latest \
server -config /root/vault.conf -dev
-
Make sure Docker is installed.
-
Clone docker-vault from GitHub
git clone https://github.com/cgswong/docker-vault.git
-
Build the docker image (change
[version]below with the appropriate version, and[your_name]as appropriate)cd docker-vault/[version] docker build -t [your_name]/vault:latest .
-
Run a docker container with that image (change [your_name] as done above)
docker run -it [your_name]/vault:latest -help
If you have any problems with or questions about this image, please contact me through a GitHub issue.
You are invited to contribute new features, fixes, or updates, large or small; I'm always thrilled to receive pull requests, and I'll do my best to process them as fast as I can.
Before you start to code, I recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.