Self-host Odoo with Levelrail
An all-in-one business suite covering CRM, sales, inventory, accounting, and a website builder.
- Authorodoo
- LicenceLGPL-3.0-only
- Memory2 GiB
- Archarm64
- Services2
How to self-host Odoo
-
Pull the images
2 images are pulled on your server.
Show images
postgres:16-alpineodoo:18
-
Create the app
2 services start in a single Compose app, with 3 named volume mounts for your data, on port 8069.
-
Fill in the secrets
2 secrets are generated and stored encrypted, 4 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.
Odoo requirements
- Memory
- About 2 GiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8069
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- LGPL-3.0-only, copyleft 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 8069 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 Odoo. 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 Odoo docs page.
Deploy Odoo your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Odoo from the CLI
levelrail-cli templates deploy odoo --name my-odoo Deploy Odoo with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/odoo/deploy Odoo configuration
Odoo services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | postgres:16-alpine | none | odoo_db_data -> /var/lib/postgresql/data |
| odoo | odoo:18 | 8069 | odoo_web_data -> /var/lib/odooodoo_addons -> /mnt/extra-addons |
Odoo environment variables
| Variable | Service | Value |
|---|---|---|
| POSTGRES_DB | db | Preset by the template |
| POSTGRES_PASSWORD | db | Generated at deploy |
| POSTGRES_USER | db | Preset by the template |
| HOST | odoo | Preset by the template |
| PASSWORD | odoo | Generated at deploy |
| USER | odoo | Preset by the template |
Ports and volumes
- Ports
- 8069
- Volumes
- 3 named mounts: odoo_db_data -> /var/lib/postgresql/data, odoo_web_data -> /var/lib/odoo, odoo_addons -> /mnt/extra-addons
Odoo FAQ
How much memory does Odoo need?
The catalog lists about 2 GiB of memory for Odoo across its 2 services.
Does Odoo run on arm64?
For Odoo, an arm64 image is published; amd64 is image published.
What licence is Odoo under?
Odoo is licensed under LGPL-3.0-only, which is copyleft, so changes you distribute must be shared under the same terms.
Does Odoo need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Odoo bundle?
The template includes Postgres, running as its own service.
Which ports does Odoo use?
Odoo listens on port 8069 inside the stack.
Where does Odoo keep its data?
In named volumes: odoo_db_data mounted at /var/lib/postgresql/data, odoo_web_data mounted at /var/lib/odoo and odoo_addons mounted at /mnt/extra-addons.
Can I deploy Odoo 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 Odoo, 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 postgres:16-alpine, odoo:18 is what you deploy there.