Host Odoo 17 Community on VPS: complete Docker installation

Why self-host Odoo Community

What Odoo 17 Community includes

• CRM: sales pipeline, leads, activities and customer tracking
• Sales: quotes, purchase orders, pricing and payment terms
• Accounting: chart of accounts, journals, bank reconciliation, VAT
• Invoicing: customer and supplier invoices, automated reminders, payments
• Inventory: stock management, locations, replenishment rules
• Purchasing: purchase requests, tenders and supplier tracking
• Human Resources: employees, contracts, leave and attendance
• Email Marketing: mailing lists, campaigns and send statistics
• Website & e-commerce: page builder, integrated online store
• Helpdesk: customer ticketing, SLA and self-service portal

Differences between Community and Enterprise

Scroll the table

VPS requirements for hosting Odoo 17

Install Odoo 17 with Docker Compose

1. 01

   Create the directory structure

   Connect via SSH to your VPS and create the working tree:

   mkdir -p /opt/odoo/{data,addons,config,backups}
   cd /opt/odoo

   These folders will hold persistent data, custom modules, Odoo configuration and backups respectively.

2. 02

   Write the docker-compose.yml file

   Create /opt/odoo/docker-compose.yml with the following content:

   services:
     db:
       image: postgres:16
       restart: unless-stopped
       environment:
         POSTGRES_DB: postgres
         POSTGRES_USER: odoo
         POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
       volumes:
         - ./data/postgres:/var/lib/postgresql/data
       healthcheck:
         test: ["CMD-SHELL", "pg_isready -U odoo"]
         interval: 10s
         retries: 5
   
     odoo:
       image: odoo:17.0
       restart: unless-stopped
       depends_on:
         db:
           condition: service_healthy
       environment:
         HOST: db
         USER: odoo
         PASSWORD: ${POSTGRES_PASSWORD}
       volumes:
         - ./data/odoo:/var/lib/odoo
         - ./addons:/mnt/extra-addons
         - ./config/odoo.conf:/etc/odoo/odoo.conf
       ports:
         - "127.0.0.1:8069:8069"
         - "127.0.0.1:8072:8072"

   Note that ports are only exposed on localhost — the reverse proxy handles external access.

3. 03

   Create the .env file and Odoo configuration

   Create /opt/odoo/.env:

   POSTGRES_PASSWORD=$(openssl rand -hex 32)
   echo "POSTGRES_PASSWORD=${POSTGRES_PASSWORD}" > /opt/odoo/.env

   Then create /opt/odoo/config/odoo.conf:

   [options]
   db_host = db
   db_port = 5432
   db_user = odoo
   db_password = ${POSTGRES_PASSWORD}
   addons_path = /usr/lib/python3/dist-packages/odoo/addons,/mnt/extra-addons
   admin_passwd = REPLACE_WITH_A_STRONG_PASSWORD
   without_demo = all
   workers = 4
   max_cron_threads = 2
   limit_memory_hard = 2684354560
   limit_memory_soft = 2147483648

4. 04

   Configure the reverse proxy with Caddy

   Caddy is the simplest choice: it handles TLS automatically via Let's Encrypt. Install it and create /etc/caddy/Caddyfile:

   odoo.yourdomain.com {
       reverse_proxy 127.0.0.1:8069
   
       # WebSocket support for real-time notifications
       handle /websocket {
           reverse_proxy 127.0.0.1:8072
       }
   
       header {
           X-Frame-Options SAMEORIGIN
           X-Content-Type-Options nosniff
           Strict-Transport-Security "max-age=31536000; includeSubDomains"
       }
   
       encode gzip
   }

   Reload Caddy: systemctl reload caddy.

5. 05

   Start the containers

   From /opt/odoo, run:

   docker compose up -d

   Follow the startup logs:

   docker compose logs -f odoo

   Odoo takes 30 to 60 seconds to initialise. You will see HTTP service (werkzeug) running when it is ready.

6. 06

   Access the interface and create the database

   Open https://odoo.yourdomain.com/web/database/manager in your browser. Enter the master password (admin_passwd) defined in odoo.conf, choose a database name, language and administrator email, then click Create. The first initialisation takes 2 to 5 minutes depending on the selected modules.

Configure the database and instance

Configure automated backups

#!/bin/bash
DATE=$(date +%Y%m%d_%H%M%S)
BACKUP_DIR=/opt/odoo/backups
DB_NAME=your_database

docker compose -f /opt/odoo/docker-compose.yml exec -T db \
  pg_dump -U odoo ${DB_NAME} | gzip > ${BACKUP_DIR}/odoo_${DATE}.sql.gz

# Retain 7 days
find ${BACKUP_DIR} -name "odoo_*.sql.gz" -mtime +7 -delete

Activate key modules after installation

• Sales (sale_management): quotes, orders, customer portal — core module for any commercial activity
• Accounting (account_accountant): chart of accounts, VAT, bank reconciliation, closings
• Inventory (stock): multi-warehouse management, lots and serial numbers, replenishment rules
• Purchasing (purchase): purchase requests, tenders, receiving and supplier invoicing
• Human Resources (hr): employee file, organisational structure, HR documents
• Helpdesk (helpdesk): ticketing, SLA, customer self-service portal — Community includes basic features
• Website (website): page builder, blog, contact forms
• E-Commerce (website_sale): online store, cart, payment — activated alongside the Website module

Optimise your instance performance

1. 07

   Adjust the number of workers

   In odoo.conf, the workers parameter controls the number of Python processes handling HTTP requests. The practical rule: workers = (vCPU × 2) + 1. On a 4 vCPU VPS, set workers = 4. Below 2, Odoo runs in single-process mode, which blocks long requests (imports, reports).

2. 08

   Configure memory limits

   Odoo kills workers that exceed defined limits to prevent memory leaks.

   limit_memory_soft = 2147483648   # 2 GB: graceful end signal
   limit_memory_hard = 2684354560   # 2.5 GB: immediate kill

   On 8 GB RAM with 4 workers + PostgreSQL, these values are consistent. Increase them if your reports are slow or workers restart frequently (docker compose logs odoo | grep killed).

3. 09

   Limit crons to avoid CPU saturation

   The max_cron_threads = 2 parameter reserves 2 threads for scheduled tasks (emails, replenishment, reports). Beyond that, crons compete with HTTP workers. On a server dedicated to Odoo, you can go up to 4, but start conservatively.

4. 10

   Enable Redis session storage (optional)

   By default, Odoo stores sessions on disk. On shared volumes or with frequent restarts, this can cause disconnections. Add a Redis service to docker-compose.yml and configure:

   session_store = redis
   redis_url = redis://redis:6379

   This option is especially useful if you plan a multi-instance architecture in the future.

Secure the Odoo instance in production

dbfilter = ^your_database$
list_db = False

Hosting comparison: self-hosted VPS vs Odoo SaaS

Scroll the table