Self-host OpenBao with Levelrail
OpenBao, the open source secrets manager forked from Vault, with integrated Raft storage. It is reachable only from services in this project at openbao:8200 over plain HTTP and is not published on the host.
- Authoropenbao
- LicenceMPL-2.0
- Memory256 MiB
- Archarm64
- Services1
How to self-host OpenBao
-
Pull the images
One image is pulled on your server.
Show images
ghcr.io/openbao/openbao:2.7.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.
After the first start
- OpenBao starts uninitialized and sealed. Open the app console and run bao operator init, then bao operator unseal with the printed keys. Keep the unseal keys and root token offline.
- Plain HTTP is for the internal network only. Attach a domain with HTTPS before anything outside this project talks to it.
OpenBao 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
- MPL-2.0, copyleft license
- 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 OpenBao. 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 OpenBao docs page.
Deploy OpenBao your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy OpenBao from the CLI
levelrail-cli templates deploy openbao --name my-openbao Deploy OpenBao with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/openbao/deploy OpenBao configuration
OpenBao services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| openbao | ghcr.io/openbao/openbao:2.7.2 | 8200 | openbao_data -> /openbao/file |
OpenBao environment variables
| Variable | Service | Value |
|---|---|---|
| BAO_ADDR | openbao | Preset by the template |
| BAO_LOCAL_CONFIG | openbao | Preset by the template |
Ports and volumes
- Ports
- 8200
- Volumes
- 1 named mount: openbao_data -> /openbao/file
OpenBao FAQ
How much memory does OpenBao need?
The catalog lists about 256 MiB of memory for OpenBao.
Does OpenBao run on arm64?
For OpenBao, an arm64 image is published; amd64 is image published.
What licence is OpenBao under?
OpenBao is licensed under MPL-2.0, which is copyleft, so changes you distribute must be shared under the same terms.
Does OpenBao need configuration before it starts?
No. The template fills in its own defaults.
Which ports does OpenBao use?
OpenBao listens on port 8200 inside the stack.
Where does OpenBao keep its data?
In a named volume: openbao_data mounted at /openbao/file.
Can I deploy OpenBao 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 openbao for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image ghcr.io/openbao/openbao:2.7.2 is what you deploy there.