Self-host Vault with Levelrail
HashiCorp Vault for secrets storage, encryption as a service, and dynamic credentials, with integrated Raft storage. Vault is reachable only from services in this project at vault:8200 over plain HTTP and is not published on the host. It starts uninitialized and sealed: run vault operator init and vault operator unseal from the app console, keep the unseal keys and root token offline, and put a domain with HTTPS in front of it before anything outside this project talks to it.
- Authorhashicorp
- LicenceBUSL-1.1
- Memory256 MiB
- Archarm64
- Services1
How to self-host Vault
-
Pull the images
One image is pulled on your server.
Show images
hashicorp/vault:2.1.2
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 8200.
-
Fill in the secrets
2 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Vault requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8200
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- BUSL-1.1, source available
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Vault. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Vault docs page.
Deploy Vault your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Vault from the CLI
levelrail-cli templates deploy vault --name my-vault Deploy Vault with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/vault/deploy Vault configuration
Vault services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| vault | hashicorp/vault:2.1.2 | 8200 | vault_data -> /vault/file |
Vault environment variables
| Variable | Service | Value |
|---|---|---|
| VAULT_ADDR | vault | Preset by the template |
| VAULT_LOCAL_CONFIG | vault | Preset by the template |
Ports and volumes
- Ports
- 8200
- Volumes
- 1 named mount: vault_data -> /vault/file
Vault FAQ
How much memory does Vault need?
The catalog lists about 256 MiB of memory for Vault.
Does Vault run on arm64?
For Vault, an arm64 image is published; amd64 is image published.
What licence is Vault under?
Vault is licensed under BUSL-1.1, which is source-available, so read the terms before commercial use.
Does Vault need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Vault use?
Vault listens on port 8200 inside the stack.
Where does Vault keep its data?
In a named volume: vault_data mounted at /vault/file.
Can I deploy Vault on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id vault for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image hashicorp/vault:2.1.2 is what you deploy there.