Self-host Inbucket with Levelrail
Disposable mail server that catches mail for any address and shows it in a web inbox, for testing apps without sending real email.
- Authorinbucket
- LicenceMIT
- Memory64 MiB
- Services1
How to self-host Inbucket
-
Pull the images
One image is pulled on your server.
Show images
inbucket/inbucket:3.2.0
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on ports 9000, 2500.
-
Fill in the secrets
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
- Point your app at port 2500 and open the address to read what it sent. It has no login, so keep it private.
Inbucket requirements
- Memory
- About 64 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 9000, 2500
- 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.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Inbucket. 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 Inbucket docs page.
Deploy Inbucket your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Inbucket from the CLI
levelrail-cli templates deploy inbucket --name my-inbucket Deploy Inbucket with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/inbucket/deploy Inbucket configuration
Inbucket services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| inbucket | inbucket/inbucket:3.2.0 | 9000, 2500 | data -> /storage |
Inbucket environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 9000, 2500
- Volumes
- 1 named mount: data -> /storage
Inbucket FAQ
How much memory does Inbucket need?
The catalog lists about 64 MiB of memory for Inbucket.
Does Inbucket run on arm64?
For Inbucket, arm64 support is not confirmed; amd64 is unknown.
What licence is Inbucket under?
Inbucket is licensed under MIT, which is permissive, with few conditions on reuse.
Does Inbucket need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Inbucket use?
Inbucket listens on ports 9000 and 2500 inside the stack.
Where does Inbucket keep its data?
In a named volume: data mounted at /storage.
Can I deploy Inbucket 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 Inbucket, 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 inbucket/inbucket:3.2.0 is what you deploy there.