Self-host Redis with Levelrail

The Redis in-memory data store on the BSD licensed 7.2 line, with append-only persistence and a generated password. It is not published on the host, so reach it from other services in this project at redis:6379.

  • Authorredis
  • LicenceBSD-3-Clause
  • Memory256 MiB
  • Services1

How to self-host Redis

  1. Pull the images

    One image is pulled on your server.

    Show images
    • redis:7.2.7-alpine
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 6379.

  3. Fill in the secrets

    2 secrets are generated and stored encrypted, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

After the first start

  • Read the generated password from the app secrets, then connect from a service in the same project with redis://:PASSWORD@redis:6379.

Redis requirements

Memory
About 256 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
6379
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
BSD-3-Clause, permissive 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 Redis. 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 Redis docs page.

Deploy Redis your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Redis from the CLI

levelrail-cli templates deploy redis --name my-redis

Deploy Redis with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/redis/deploy

Redis configuration

Redis services

ServiceImagePortsVolumes
redis redis:7.2.7-alpine 6379 redis_data -> /data

Redis environment variables

VariableServiceValue
REDISCLI_AUTH redis Generated at deploy
REDIS_PASSWORD redis Generated at deploy

Ports and volumes

Ports
6379
Volumes
1 named mount: redis_data -> /data

Redis FAQ

How much memory does Redis need?

The catalog lists about 256 MiB of memory for Redis.

Does Redis run on arm64?

For Redis, arm64 support is not confirmed; amd64 is unknown.

What licence is Redis under?

Redis is licensed under BSD-3-Clause, which is permissive, with few conditions on reuse.

Does Redis need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which database does Redis bundle?

The template includes Redis, running as part of the stack.

Which ports does Redis use?

Redis listens on port 6379 inside the stack.

Where does Redis keep its data?

In a named volume: redis_data mounted at /data.

Can I deploy Redis on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Redis, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image redis:7.2.7-alpine is what you deploy there.

levelrail-cli templates deploy redis --name my-redis