{"id":19391,"date":"2025-10-23T11:17:10","date_gmt":"2025-10-23T08:17:10","guid":{"rendered":"https:\/\/unihost.com\/help\/?p=19391"},"modified":"2026-11-06T17:00:51","modified_gmt":"2026-11-06T14:00:51","slug":"installing-odoo-with-portainer","status":"publish","type":"post","link":"https:\/\/unihost.com\/help\/installing-odoo-with-portainer\/","title":{"rendered":"How to Install Odoo with Portainer (Docker)"},"content":{"rendered":"
\n

Odoo Community can be deployed on your VPS using the Unihost application template in Portainer. Open Templates, choose Odoo, enter the PostgreSQL credentials and deploy the stack. Then configure the database master password, persistent storage, a domain with HTTPS, and backups. This guide also covers custom addons and safe image updates.<\/p>\n

Compatibility: Linux with Docker Engine, Portainer and the Odoo Community Docker image. Odoo 20.0 is the latest stable major release as of November 6, 2026.<\/p>\n

Requirements<\/h2>\n

You need a VPS with Docker and Portainer, administrator access, PostgreSQL and a domain. The original Unihost deployment uses Nginx Proxy Manager (NPM); Traefik is an alternative for HTTPS. For a small installation, 2 vCPU, 4 GB RAM and 40 GB SSD are a starting estimate, not an official universal requirement.<\/p>\n

For Portainer basics, see What is Portainer?<\/a>.<\/p>\n

Steps<\/h2>\n

Step 1. Select the Odoo template<\/h3>\n

Sign in to Portainer, select the local environment and open Templates \u2192 Application \u2192 Odoo<\/strong>. Fill in the database username and a strong password, then deploy the application. The resulting stack is named odoo-app<\/strong> in the original Unihost template.<\/p>\n

\"Select<\/p>\n

\"Choose<\/p>\n

\"Enter<\/p>\n

\"Check<\/p>\n

docker ps<\/pre>\n
Step 2. Set up PostgreSQL and storage<\/h3>\n
The official Odoo Docker image connects to PostgreSQL using these environment variables. The credentials must match the PostgreSQL container.<\/p>\n\n\n\n\n\n\n\n
Variable<\/th>\nPurpose<\/th>\n<\/tr>\n<\/thead>\n
HOST<\/td>\nPostgreSQL service name<\/td>\n<\/tr>\n
USER<\/td>\nPostgreSQL user<\/td>\n<\/tr>\n
PASSWORD<\/td>\nPostgreSQL password<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
HOST=db\r\nUSER=odoo\r\nPASSWORD=YOUR_STRONG_DB_PASSWORD<\/pre>\n
Keep Odoo data at \/var\/lib\/odoo<\/strong> and custom modules at \/mnt\/extra-addons<\/strong>. PostgreSQL also needs its own persistent data volume. Example mounts for the Odoo service:<\/p>\n
volumes:\r\n  - odoo_data:\/var\/lib\/odoo\r\n  - .\/addons:\/mnt\/extra-addons<\/pre>\n
This is a Compose fragment, not a replacement for the Unihost template. Do not remove existing volumes when recreating containers.<\/p>\n
Step 3. Protect the master password and configure workers<\/h3>\n
Set a unique master password in odoo.conf<\/strong> (normally mounted at \/etc\/odoo\/odoo.conf). It protects database management and is different from the Odoo user password. If the template supplies default admin credentials, change them before exposing the site.<\/p>\n
[options]\r\nadmin_passwd = YOUR_UNIQUE_MASTER_PASSWORD<\/pre>\n
For a reverse-proxied production deployment, enable proxy mode and size the number of workers to available CPU and RAM. The following is an example, not a universal tuning recommendation:<\/p>\n
[options]\r\nworkers = 2\r\nproxy_mode = True<\/pre>\n
Step 4. Configure a domain and HTTPS<\/h3>\n
To publish Odoo using Nginx Proxy Manager (NPM), follow these steps:<\/p>\n
    \n
  1. Create a DNS A record for odoo.example.com pointing to your VPS public IP.<\/li>\n
  2. Open NPM \u2192 Hosts \u2192 Proxy Hosts \u2192 Add Proxy Host.<\/li>\n
  3. Set Domain Names to odoo.example.com and Scheme to http.<\/li>\n
  4. Set Forward Hostname \/ IP to the Odoo service hostname reachable from NPM, and Forward Port to 8069.<\/li>\n
  5. Enable Websockets Support when needed by your configuration. Under SSL, request a Let\u2019s Encrypt certificate, enable Force SSL and save.<\/li>\n<\/ol>\n
    Use proxy_mode = True in odoo.conf when Odoo is behind a trusted proxy. With multiple workers, configure the evented\/WebSocket endpoint according to your Odoo version. NPM and Odoo must have Docker network connectivity. Avoid exposing 8069 directly to the internet.<\/p>\n
    Nginx Proxy Manager installation and HTTPS configuration<\/a><\/p>\n
    Traefik with Portainer is an alternative for HTTPS.<\/p>\n
    odoo.example.com -> SERVER_IP\r\nForward hostname: odoo-app\r\nForward port: 8069<\/pre>\n
    \"Configure<\/p>\n
    Restrict direct access to port 8069. Do not treat the HTTP login screen shown in an older screenshot as the desired public configuration.<\/p>\n
    Step 5. Install custom addons<\/h3>\n
    Mount your trusted module folder at \/mnt\/extra-addons, confirm its presence in addons_path, restart Odoo, enable developer mode and update the Apps list before installing the module. Use only modules compatible with your Odoo version.<\/p>\n
    \/mnt\/extra-addons\/my_custom_module\/<\/pre>\n
    Step 6. Back up Odoo<\/h3>\n
    Use the Odoo Database Manager to download a ZIP backup that includes the filestore, or back up PostgreSQL with pg_dump. A database-only dump does not include attachments stored in the Odoo filestore.<\/p>\n
    docker exec DB_CONTAINER pg_dump -U odoo -d DATABASE_NAME -Fc > odoo-backup.dump<\/pre>\n
    Keep copies of PostgreSQL, the Odoo filestore and configuration outside the VPS. Verify restoration periodically.<\/p>\n
    Step 7. Update the Docker image<\/h3>\n
    Back up the database, filestore and configuration, then check the release notes and addon compatibility. For an installation already on the same major version, update the compatible image tag in Portainer and recreate the service without removing volumes. Upgrading from Odoo 19 to 20 requires a database migration, not just a new image.<\/p>\n
    odoo:20.0<\/pre>\n
    Verify<\/h2>\n
    Check that the Odoo and PostgreSQL containers are running, the site loads over HTTPS, users can sign in, modules are available and backups can be restored.<\/p>\n
    docker ps\r\ndocker logs --tail 50 ODOO_CONTAINER<\/pre>\n
    \"Check<\/p>\n
    Troubleshooting<\/h2>\n
    Odoo cannot connect to PostgreSQL<\/h3>\n
    Check HOST, USER, PASSWORD, the database service and the shared Docker network.<\/p>\n
    The domain or HTTPS does not work<\/h3>\n
    Check DNS, NPM or Traefik, TLS and access to internal port 8069.<\/p>\n
    A custom module is missing<\/h3>\n
    Check the mounted \/mnt\/extra-addons directory, addons_path, module compatibility and the refreshed Apps list.<\/p>\n
    Odoo responds slowly<\/h3>\n
    Check CPU, RAM, PostgreSQL performance and workers; increase VPS resources if necessary.<\/p>\n
    FAQ<\/h2>\n
    Can I run Odoo Enterprise in Docker?<\/h3>\n
    Yes, with a valid Enterprise subscription and the corresponding addons. The official Odoo image primarily provides Community.<\/p>\n
    How do I install custom modules?<\/h3>\n
    Mount compatible addons at \/mnt\/extra-addons, add the path in Odoo configuration, restart and update the Apps list.<\/p>\n
    How do I back up Odoo?<\/h3>\n
    Use Database Manager with filestore included, or pg_dump plus a separate copy of \/var\/lib\/odoo and configuration.<\/p>\n
    What server size do I need for Odoo?<\/h3>\n
    For a small deployment, 2 vCPU, 4 GB RAM and 40 GB SSD are a starting estimate. Size workers, RAM and storage for actual users and modules.<\/p>\n
    Related Articles<\/h2>\n