Self-host Wallabag with Levelrail
A read-it-later app that saves web articles in a clean, distraction-free format.
- Authorwallabag
- LicenceMIT
- Memory512 MiB
- Archarm64
- Services1
How to self-host Wallabag
-
Pull the images
One image is pulled on your server.
Show images
wallabag/wallabag:2.6.14
-
Create the app
One service starts in a single Compose app, with 2 named volume mounts for your data, on port 80.
-
Fill in the secrets
1 secret is generated and stored encrypted, 1 setting is 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.
Wallabag requirements
- Memory
- About 512 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 80
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 80 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Wallabag. 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 Wallabag docs page.
Deploy Wallabag your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Wallabag from the CLI
levelrail-cli templates deploy wallabag --name my-wallabag Deploy Wallabag with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/wallabag/deploy Wallabag configuration
Wallabag services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| wallabag | wallabag/wallabag:2.6.14 | 80 | wallabag_data -> /var/www/wallabag/datawallabag_images -> /var/www/wallabag/web/assets/images |
Wallabag environment variables
| Variable | Service | Value |
|---|---|---|
| SYMFONY__ENV__DOMAIN_NAME | wallabag | Preset by the template |
| SYMFONY__ENV__SECRET | wallabag | Generated at deploy |
Ports and volumes
- Ports
- 80
- Volumes
- 2 named mounts: wallabag_data -> /var/www/wallabag/data, wallabag_images -> /var/www/wallabag/web/assets/images
Wallabag FAQ
How much memory does Wallabag need?
The catalog lists about 512 MiB of memory for Wallabag.
Does Wallabag run on arm64?
For Wallabag, an arm64 image is published; amd64 is image published.
What licence is Wallabag under?
Wallabag is licensed under MIT, which is permissive, with few conditions on reuse.
Does Wallabag need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Wallabag use?
Wallabag listens on port 80 inside the stack.
Where does Wallabag keep its data?
In named volumes: wallabag_data mounted at /var/www/wallabag/data and wallabag_images mounted at /var/www/wallabag/web/assets/images.
Can I deploy Wallabag 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 wallabag for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image wallabag/wallabag:2.6.14 is what you deploy there.