odoo-it/docker-odoo

A production and development ready Odoo docker image

Docker Odoo

A docker image ready to run Odoo, either for dev or prod deployments, that doesn't contain odoo.

Usage

Getting started

This image is prepared to run Odoo, but it doesn't include it. You're expected to cook an image for your project and include whatever Odoo fork you want in it. This gives you a lot of freedom to use this image however you want.

As an example, assuming you have a local Odoo fork in ./src and your project addons repositories in ./repositories, you could create a project image like this:

Dockerfile

FROM ghcr.io/odoo-it/docker-odoo:15.0.2.0.3 AS base

# Install project requirements
USER root
COPY --chown=odoo:odoo ./requirements.txt $RESOURCES/requirements.txt
RUN pip install -r $RESOURCES/requirements.txt
USER odoo

# Copy sources
COPY --chown=odoo:odoo repositories $SOURCES/repositories
COPY --chown=odoo:odoo src $SOURCES/user
RUN ln -s $SOURCES/repositories/odoo/odoo $SOURCES/odoo && pip-install-odoo

docker-compose.yaml

services:

  odoo:
    build:
      context: .
    depends_on:
      db:
        condition: service_healthy
    ports:
      - "8069:8069"
      - "8072:8072"
    tty: true
    stdin_open: true
    volumes:
      - ./repositories:/home/odoo/src/repositories:rw,z
      - ./src:/home/odoo/src/user:rw,z
      - filestore:/home/odoo/data
    environment:
      PGHOST: db
      PGDATABASE: odoodb

  db:
    image: postgres:15
    environment:
      POSTGRES_USER: odoo
      POSTGRES_PASSWORD: odoo
      POSTGRES_DB: postgres
    volumes:
      - db:/var/lib/postgresql/data
    healthcheck:
      test: [ "CMD", "pg_isready", "-q", "-h", "localhost" ]
      interval: 5s
      timeout: 5s
      retries: 5

volumes:
  db:
  filestore:

Versions

Tag	Description	Example
<odoo>	Targets the latest release for this Odoo version	17.0, 16.0, master
<odoo>.<release>	Targets a specific release for an Odoo version	17.0.3.0.0
<odoo>-latest	Targets the latest unreleased/unstable version for this Odoo version	17.0-latest
<odoo>-<sha>	Targets the a specific commit for this Odoo version	17.0-a1bsz6

Directory structure

Basically, every directory you have to worry about is found inside /home/odoo. The directory structure is similar to odoo.sh, but not exactly the same. This is the structure:

src/
    odoo/
    repositories/
    user/
data/
    addons/
    filestore/
    sessions/
.config/
    odoo.conf
.resources/
    conf.d/
    entrypoint.d/

Path	Description
src/odoo	Empty. Path where odoo source code is expected to be.
src/repositories	Optional. Path where your project's addon repositories are expected to be.
src/user	Optional. Path where your project's local source is expected to be. Submodules will be loaded too.
data/	Odoo data directory. You usually want to persist it.
.config/odoo.conf	Odoo configuration file. Generated automatically from conf.d.
.resources/conf.d	Files here will be environment-variable-expanded and concatenated in odoo.conf in the entrypoint.
.resources/entrypoint.d	Any executables found here will be run when you launch your container.

Runtime environment variables

The following variables can customize entrypoint behaviour and odoo.conf:

Odoo Configuration

Database

• PGHOST
• PGPORT
• PGDATABASE
• PGUSER
• PGPASSWORD

SMTP

• SMTP_SERVER
• SMTP_PORT
• SMTP_USER
• SMTP_PASSWORD
• SMTP_SSL
• EMAIL_FROM

Performance

• WORKERS
• MAX_CRON_THREADS
• DB_MAXCONN
• LIMIT_MEMORY_HARD
• LIMIT_MEMORY_SOFT
• LIMIT_TIME_CPU
• LIMIT_TIME_REAL
• LIMIT_TIME_REAL_CRON

Other

• ADMIN_PASSWORD
• PROXY_MODE
• UNACCENT
• LOG_LEVEL
• SERVER_WIDE_MODULES

Entrypoint

• ODOO_CONF: Extra odoo configuration to be added to odoo.conf.
• CUSTOM_REQUIREMENTS: Custom pip requirements.txt, to be installed at runtime.
• CUSTOM_ENTRYPOINT: Custom script to be executed at runtime.
• AUTO_UPDATE_MODULES: Run click-odoo-update to automatically update addons.
• PGTIMEOUT: Seconds to wait for the postgres server to respond. Set to 0 to disable. (default: 10)

Development

Build

This project uses Bake to build the different images.

The build configurations are defined in the docker-bake.hcl file.

Here are some useful commands:

Command	Description
docker buildx bake	Build the default version
VERSION=17.0 docker buildx bake	Build the specified version (e.g: 17.0, master, ...)
VERSION=17.0 docker buildx bake --set="*.platform=linux/amd64"	Build for amd64 arch only