Deploy Odoo with Docker

Odoo Docker Deployment provides a starting configuration for self-hosted Odoo with PostgreSQL, persistent storage, environment variables, and optional reverse-proxy planning. It covers local development and production-oriented scenarios while requiring environment-specific validation before the configuration is considered ready.

The Compose example separates the database and application services on an internal network. PostgreSQL has a readiness healthcheck, and Odoo waits for the service to become healthy. Persistent volumes retain database and Odoo data, while mounted directories provide custom addons and application configuration. Published Odoo ports bind to loopback rather than exposing the application directly to the network.

Use it when starting a Docker development environment, preparing a VPS or cloud deployment, diagnosing container startup or database connection failures, or planning SSL termination in front of an existing setup. Describe the deployment scenario and actual errors so configuration and diagnosis match the environment.

This workflow covers self-hosted containers rather than Odoo.sh. Horizontal scaling needs shared filestore design beyond this setup. TLS, proxy, and database-selection hardening require separate validation, and full reverse-proxy configuration should follow the official Odoo deployment guidance. Verify addons paths after image upgrades.

Inputs include the target deployment, database credentials, private administrative configuration, custom addons, and measured resource requirements. Outputs include a docker-compose.yml and odoo.conf starting point plus operational and diagnostic guidance. Configuration includes workers, cron threads, memory thresholds, CPU and real-time limits, request limits, and logging settings, but these values require sizing for the actual workload.

Compose expands variables in the Compose file, not arbitrary mounted application configuration. Required secrets must be rendered through an approved private mechanism without printing them. The official container entrypoint receives the database password through its PASSWORD environment setting. Use container output for logs unless a private writable log volume is configured.

A log-inspection command is:

docker compose logs -f odoo

Module updates change schema and data. Stop normal workers, back up both database and filestore consistently, run one reviewed maintenance instance, verify, and then restart. A SQL dump alone is insufficient for complete Odoo recovery; prove the restore in staging.

Nginx can terminate SSL with Let's Encrypt or Certbot. PostgreSQL stays on the internal Docker network rather than a public database port. Keep credentials out of Compose text and use approved secrets or environment configuration. Pin a reviewed image digest because even a version-series tag is mutable. Measure HTTP, cron, database, and operating-system memory together rather than trusting a CPU-based worker heuristic.