Most Odoo Docker setups start with one line: image: odoo:19. It works, so few people look further. But the image makes choices for you about the operating system, the PDF engine, the user Odoo runs as, where your files go and how it waits for the database. Knowing those choices explains most of the surprises people hit later. This guide walks through the official image as published in November 2026. If you want to extend it with your own modules instead, see build a custom Odoo Docker image.
Where the image comes from
The image is a Docker Official Image called odoo, maintained by Odoo S.A. Its source lives in the odoo/docker repository on GitHub, with one folder per supported version: 18.0, 19.0 and 20.0 at the time of writing. The three Dockerfiles are almost identical; only the version number and the package checksum change.
Images are published for amd64, arm64 and ppc64le, so the same tag runs on an Intel server, an ARM cloud instance or an Apple Silicon laptop.
Tags: moving or pinned
Every build gets several tags. For Odoo 20, the newest build is tagged 20.0, 20 and latest, and also with a dated tag such as 20.0-20261112.
- Moving tags (
odoo:19,odoo:latest) point to a new build every couple of weeks. Two servers that pull a week apart can run different code. - Dated tags (
odoo:19.0-20261112) stay on one build. Older dated tags remain on Docker Hub.
For production, pin a dated tag or an image digest, and move to a newer one on purpose, after testing it. Never let latest decide which major version you run.
What the Dockerfile installs
| Layer | What it adds | Why it matters |
|---|---|---|
| Base | Ubuntu 24.04 (ubuntu:noble) | System packages come from Ubuntu, not Debian, so look up package names for Ubuntu. |
| System libraries | Python libraries packaged by Ubuntu (for QR codes, phone numbers, LDAP, spreadsheets and more), Noto CJK fonts, node-less | Many Odoo dependencies are already present, installed as system packages rather than with pip. |
| PDF engine | wkhtmltopdf 0.12.6.1 from the project's own packages (the Ubuntu 22.04 build), checked against a fixed checksum | Odoo prints invoices and reports to PDF through it, and recommends this version. |
| Database client | postgresql-client from the PostgreSQL project's own repository | Gives psql and pg_dump for backups. It is the client only. |
| Right-to-left CSS | rtlcss, installed with npm, after which npm is removed | Needed for Arabic, Hebrew and other right-to-left languages. |
| Odoo | The Odoo Community Debian package from Odoo's nightly server, pinned to a dated build and verified with a checksum | The code lives in the system Python path, not in a Git checkout. |
The image holds Odoo Community only. There is no Enterprise code in it; Enterprise modules have to be added as a separate addons folder. There is also no PostgreSQL server. The database always runs somewhere else, usually in a second container.
User, ports and volumes
The last part of the Dockerfile sets how the container runs:
- User: Odoo runs as the
odoouser, not root. Files you mount must be readable by that user, and folders Odoo writes to must be writable by it. This is a common cause of "permission denied" errors on a fresh setup. - Ports:
8069for the web interface,8072for live updates (websocket or longpolling, used by chat and notifications when workers are enabled) and8071, a leftover from older XML-RPC over SSL. - Volumes:
/var/lib/odooholds the filestore, where attachments and images are kept, and sessions./mnt/extra-addonsis where your own modules go.
If you don't map /var/lib/odoo to a named volume or a bind mount, Docker puts it on an anonymous volume. A new container won't reuse it, and docker compose down -v deletes it. A database backup without the filestore restores an Odoo with every attachment missing.
The default odoo.conf
The image ships a configuration file at /etc/odoo/odoo.conf, and the ODOO_RC variable points Odoo at it. Only a few lines are active: the addons path (/mnt/extra-addons), the data directory (/var/lib/odoo) and, on 19.0 and 20.0, http_interface = 0.0.0.0. Everything else is commented out as a reference.
That means the defaults are development defaults. workers is 0, so Odoo runs as one threaded process. No master password is set, and the database manager is reachable. Before going live, mount your own odoo.conf over the default one and set at least workers, memory and time limits, admin_passwd, list_db = False and proxy_mode. The Odoo server configuration guide explains each setting.
How the entrypoint starts Odoo
The container's entrypoint is a short shell script. When the command is odoo (the default), it:
- Works out the database host, port, user and password. It reads them from environment variables such as
HOST,USERandPASSWORD, falling back todb,5432,odooandodoo. A password can also come from a file named inPASSWORD_FILE, which suits Docker secrets. - Passes each value to Odoo on the command line. On 19.0 and 20.0 it skips a value the config file already sets, or one given in the standard PostgreSQL variables (
PGHOST,PGUSERand so on), which those versions read directly. The 18.0 script always passes them. - Runs a small Python script that tries to connect to PostgreSQL once a second for up to 30 seconds, and stops with an error if the database never answers.
- Starts Odoo with any extra arguments you gave.
If the command is something else, such as bash, the script simply runs it. So docker run -it odoo:19 bash gives you a shell in the image without starting Odoo.
What the image leaves to you
The official image is a clean Odoo runtime, not a hosting setup. You still need to provide:
- A PostgreSQL server, sized and backed up.
- A production
odoo.conf. - A reverse proxy with HTTPS in front of ports 8069 and 8072.
- Persistent storage for the filestore, and backups of it.
- A health check: the image does not define one, although Odoo answers on
/web/health. - Any extra Python packages your modules need.
- Enterprise modules, if you use Enterprise.
How Easy Instance uses it
Easy Instance runs this same official image rather than a home-made one. Each release pins the image by digest together with the Enterprise code from the same nightly build, so a redeploy never mixes a newer image with older Enterprise modules. Around it, the platform adds what the image leaves out: a generated production odoo.conf, a managed PostgreSQL server, Enterprise mounted read-only when you choose it, a health check on /web/health, persistent storage, SSL, daily backups and Python packages from the Packages tab. If you would rather not assemble that yourself, start a free 10-day trial.