Self-host Valkey with Levelrail
VerifiedA Redis-compatible in-memory key-value store under the Linux Foundation, with password auth and append-only persistence.
- Authorvalkey-io
- LicenceBSD-3-Clause
- Memory256 MiB
- Archarm64
- Services1
How to self-host Valkey
-
Pull the images
One image is pulled on your server.
Show images
valkey/valkey:8.0-alpine
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 6379.
-
Fill in the secrets
1 secret is generated and stored encrypted, 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.
Valkey requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 tested
- Ports
- 6379
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- BSD-3-Clause, permissive license
- Verified. Verified on arm64 with image tag 8.0-alpine. Our CI ran this exact image version and it answered on its health path. Evidence
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Valkey. 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 Valkey docs page.
Deploy Valkey your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Valkey from the CLI
levelrail-cli templates deploy valkey --name my-valkey Deploy Valkey with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/valkey/deploy Valkey configuration
Valkey services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| valkey | valkey/valkey:8.0-alpine | 6379 | valkey_data -> /data |
Valkey environment variables
| Variable | Service | Value |
|---|---|---|
| VALKEY_PASSWORD | valkey | Generated at deploy |
Ports and volumes
- Ports
- 6379
- Volumes
- 1 named mount: valkey_data -> /data
Valkey FAQ
How much memory does Valkey need?
The catalog lists about 256 MiB of memory for Valkey.
Does Valkey run on arm64?
For Valkey, arm64 is tested; amd64 is image published.
What licence is Valkey under?
Valkey is licensed under BSD-3-Clause, which is permissive, with few conditions on reuse.
Does Valkey need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Valkey bundle?
The template includes Redis, running as part of the stack.
Which ports does Valkey use?
Valkey listens on port 6379 inside the stack.
Where does Valkey keep its data?
In a named volume: valkey_data mounted at /data.
Can I deploy Valkey 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 valkey for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image valkey/valkey:8.0-alpine is what you deploy there.