Odoo Docker Hub — Official Image Tags, Versions & Usage

Odoo on Docker Hub — Overview

The official Odoo image lives at hub.docker.com/_/odoo. It is maintained by the Odoo S.A. team and published as a Docker Official Image, which means it goes through Docker's review process for security and best practices.

What the image includes:

• •Odoo Community Edition (server + web client)
• •Python 3.11+ runtime with all required Python dependencies
• •wkhtmltopdf for PDF report generation
• •Node.js and rtlcss for RTL language support
• •A minimal odoo.conf configuration
• •An entrypoint script that handles database initialization

What it does not include:

• •PostgreSQL — you provide this as a separate container or external service
• •Nginx or any reverse proxy
• •SSL certificates
• •Enterprise edition modules
• •Custom or third-party addons

The image is rebuilt and pushed whenever a new Odoo point release ships, so you get security patches without building anything yourself. For most versions, that means updates within days of an upstream release.

Image Tags & Versions

The odoo image on Docker Hub follows a consistent tagging scheme. Here is every tag you will encounter:

Tag naming rules:

• •X.0 (e.g., 18.0) — The specific major version. This is what you should use in production. It tracks the latest point release within that major version.
• •X (e.g., 18) — Alias for X.0. Functionally identical.
• •latest — Always points to the newest stable major version. Right now that is 18.0. Never use this in production because it will jump to 19.0 the moment that ships, and your database will not be compatible.

There are no separate -slim tags in the official Odoo repository. The image is already reasonably sized (roughly 700–900 MB compressed depending on version). If you need a smaller image, you will need to build your own — covered in the Building Custom Images section below.

Which tag should you pick?

• •New projects: odoo:18.0 — latest stable with all current features.
• •Existing production: Whatever major version you are already running. Do not jump major versions without a database migration.
• •Development/testing: Match your production version exactly.

Pulling & Running the Image

Start with the basics. Pull the image:

docker pull odoo:18.0

The simplest possible run — a throwaway instance for testing:

# Start PostgreSQL
docker run -d \
  --name odoo-db \
  -e POSTGRES_USER=odoo \
  -e POSTGRES_PASSWORD=odoo \
  -e POSTGRES_DB=postgres \
  postgres:16

# Start Odoo, linked to the database
docker run -d \
  --name odoo \
  --link odoo-db:db \
  -p 8069:8069 \
  odoo:18.0

Open http://localhost:8069 and you will see the database manager. Create a database and you are running Odoo.

A better minimal example with Docker Compose:

services:
  db:
    image: postgres:16
    environment:
      POSTGRES_USER: odoo
      POSTGRES_PASSWORD: odoo
      POSTGRES_DB: postgres
    volumes:
      - odoo-db-data:/var/lib/postgresql/data

  odoo:
    image: odoo:18.0
    depends_on:
      - db
    ports:
      - "8069:8069"
    environment:
      HOST: db
      USER: odoo
      PASSWORD: odoo
    volumes:
      - odoo-filestore:/var/lib/odoo

volumes:
  odoo-db-data:
  odoo-filestore:

docker compose up -d

This gives you persistent data across container restarts. For a full production-ready Compose file with Nginx, SSL, and backups, see our Odoo Docker Compose guide or generate one with the Docker Compose Generator.

Environment Variables

The Odoo Docker image accepts these environment variables to configure the database connection and server behavior:

These are the variables the entrypoint script handles. For any other Odoo configuration, you have two options:

Option 1: Mount a custom odoo.conf

volumes:
  - ./odoo.conf:/etc/odoo/odoo.conf

Your odoo.conf can include any Odoo server parameter:

[options]
addons_path = /mnt/extra-addons
admin_passwd = your-strong-master-password
db_host = db
db_port = 5432
db_user = odoo
db_password = odoo
dbfilter = ^mydb$
list_db = False
proxy_mode = True
workers = 4
limit_memory_hard = 2684354560
limit_memory_soft = 2147483648
limit_time_cpu = 600
limit_time_real = 1200

Option 2: Pass Odoo CLI flags directly

services:
  odoo:
    image: odoo:18.0
    command: -- --db-filter='^mydb$$' --without-demo=all --workers=4

Arguments after -- are passed directly to the Odoo server process. This is useful for overriding a few settings without managing a full config file.

Volume Mounts

Three paths inside the container hold data you care about:

volumes:
  - odoo-filestore:/var/lib/odoo
  - ./custom-addons:/mnt/extra-addons
  - ./odoo.conf:/etc/odoo/odoo.conf

For custom addons, the /mnt/extra-addons path is already included in the default addons_path in the image's built-in config. Just drop your modules in and restart.

Image Variants Explained

The official Odoo image ships as a single variant per version — there is no -slim or -alpine tag.

What is inside the standard image:

• •Debian base (Bookworm for 17+, Bullseye for 15–16)
• •Full Python environment with all Odoo pip dependencies
• •wkhtmltopdf (required for PDF report generation — this is the main size contributor)
• •Node.js + npm + rtlcss (for right-to-left language rendering)
• •System libraries for image processing (Pillow), XML parsing (lxml), LDAP (if needed)

Typical compressed image sizes:

If image size is a concern, you can build a custom slimmed-down image. The tradeoff: removing wkhtmltopdf saves ~200 MB but breaks PDF reports. Removing Node.js saves ~80 MB but breaks RTL support. For most deployments, the standard image is the right choice.

Building Custom Odoo Docker Images

The official image covers the base case. When you need custom Python packages, system dependencies, or third-party addons baked into the image, build your own.

Adding pip packages (e.g., for OCA modules or integrations):

FROM odoo:18.0

USER root

RUN pip3 install --no-cache-dir \
    openupgradelib \
    python-stdnum \
    phonenumbers \
    boto3

USER odoo

Adding system dependencies:

FROM odoo:18.0

USER root

RUN apt-get update && apt-get install -y --no-install-recommends \
    libcups2-dev \
    && rm -rf /var/lib/apt/lists/*

USER odoo

Baking custom addons into the image (for immutable deployments):

FROM odoo:18.0

USER root

COPY ./custom-addons /mnt/extra-addons
RUN chown -R odoo:odoo /mnt/extra-addons

USER odoo

Full production Dockerfile example:

FROM odoo:18.0

USER root

# System dependencies
RUN apt-get update && apt-get install -y --no-install-recommends \
    gcc \
    libffi-dev \
    && rm -rf /var/lib/apt/lists/*

# Python dependencies
COPY requirements.txt /tmp/requirements.txt
RUN pip3 install --no-cache-dir -r /tmp/requirements.txt \
    && rm /tmp/requirements.txt

# Custom addons
COPY ./addons /mnt/extra-addons
RUN chown -R odoo:odoo /mnt/extra-addons

# Custom config
COPY ./odoo.conf /etc/odoo/odoo.conf
RUN chown odoo:odoo /etc/odoo/odoo.conf

USER odoo

EXPOSE 8069 8072

Build and tag it:

docker build -t my-odoo:18.0 .

Then reference my-odoo:18.0 in your docker-compose.yml instead of the official image.

Community vs Enterprise Images

Community Edition is what the official odoo image on Docker Hub contains. It is open source (LGPL-3.0), free to use, and includes the core ERP modules.

Enterprise Edition adds proprietary modules (accounting features, studio, marketing automation, etc.) that require an active Odoo subscription. There is no public Enterprise image on Docker Hub.

To run Enterprise with Docker, you have two options:

Option 1: Mount Enterprise addons as a volume

If you have an Odoo Enterprise subscription, you can download the enterprise addons and mount them:

services:
  odoo:
    image: odoo:18.0
    volumes:
      - ./enterprise-addons:/mnt/enterprise
    command: -- --addons-path=/mnt/extra-addons,/mnt/enterprise

Option 2: Build a custom image with Enterprise addons

FROM odoo:18.0

USER root

# Copy Enterprise addons (not committed to public repos)
COPY ./enterprise /mnt/enterprise
RUN chown -R odoo:odoo /mnt/enterprise

USER odoo

CMD ["odoo", "--addons-path=/mnt/extra-addons,/mnt/enterprise"]

Multi-Architecture Support

The official Odoo Docker images are published for multiple architectures:

Docker automatically pulls the correct architecture for your platform. If you are developing on an M-series Mac, you get the arm64 image. When you deploy to an amd64 server, Docker pulls the amd64 variant. No configuration needed.

Building multi-arch custom images:

If you build a custom image on your M-series Mac and push it to a registry, it will only contain the arm64 variant by default. For production on amd64 servers, use Docker Buildx:

docker buildx create --use
docker buildx build \
  --platform linux/amd64,linux/arm64 \
  -t my-registry/my-odoo:18.0 \
  --push .

Version Upgrade Path with Docker

Docker makes version upgrades more structured, but the database migration is still the hard part.

Step 1: Back up everything

# Database
docker compose exec db pg_dump -U odoo mydb > backup-pre-upgrade.sql

# Filestore
docker compose exec odoo tar czf - /var/lib/odoo > filestore-backup.tar.gz

Step 2: Pull the new image

docker pull odoo:18.0  # or whatever version you're upgrading to

Step 3: Run the database upgrade

Odoo major version upgrades require the Odoo Upgrade service (upgrade.odoo.com) or manual migration scripts. You cannot simply point a new Odoo version at an old database.

For minor updates within the same major version (e.g., 18.0 January release to 18.0 March release):

docker compose down
docker compose pull
docker compose up -d
# Odoo handles minor schema updates automatically on startup

Step 4: Rollback strategy

This is why you backed up in Step 1:

# If something goes wrong, restore the database
docker compose down
docker compose exec db psql -U odoo postgres -c "DROP DATABASE mydb;"
docker compose exec db psql -U odoo postgres < backup-pre-upgrade.sql
# Revert to previous image tag in docker-compose.yml
docker compose up -d

Best Practices

These are the rules that will save you from the most common production Docker + Odoo failures:

services:
  odoo:
    image: odoo:18.0
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:8069/web/health"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 60s

services:
  odoo:
    image: odoo:18.0
    deploy:
      resources:
        limits:
          memory: 2G
          cpus: "2.0"
        reservations:
          memory: 1G
          cpus: "1.0"

Frequently Asked Questions