Odoo Docker logo

Odoo Docker

Community
ahmed-lakosha
odoo-docker

Docker infrastructure manager for Odoo — production deployment, nginx proxy, CI/CD pipelines, performance tuning, multi-version image management, container debugging, and centralized workspace orchestration for Odoo 14-19 Enterprise. v2.0 consolidates nginx, debug, and perf into natural language triggers alongside the /odoo-docker sub-command interface. <example> Context: User wants to deploy Odoo to production with Docker user: "Deploy my Odoo 17 project to production using Docker" assistant: "I will use the odoo-docker skill to generate a production docker-compose.yml with Odoo, PostgreSQL, and nginx containers, with proper volume mounts and restart policies." <commentary>Core trigger - production Docker deployment.</commentary> </example> <example> Context: User wants nginx reverse proxy configuration user: "Set up nginx as a reverse proxy in front of my Odoo Docker container" assistant: "I will use the odoo-docker skill to generate an nginx.conf with SSL termination, WebSocket longpolling proxy, and proper cache headers for Odoo static assets." <commentary>Infrastructure trigger - nginx configuration for Odoo.</commentary> </example> <example> Context: User has a crashing Docker container user: "My Odoo Docker container keeps restarting - how do I debug it?" assistant: "I will use the odoo-docker skill to check container logs, verify environment variables, inspect the Odoo config, and identify the startup failure cause." <commentary>Debugging trigger - container crash diagnosis.</commentary> </example> <example> Context: User needs nginx reverse proxy for Odoo user: "Generate nginx config for my Odoo Docker setup" assistant: "I will use the odoo-docker skill to generate an optimized nginx.conf with gzip, WebSocket proxy, caching, and rate limiting." <commentary>Nginx trigger - reverse proxy configuration.</commentary> </example> <example> Context: User's container keeps crashing user: "My Odoo container keeps restarting, help me debug it" assistant: "I will use the odoo-docker skill to check container status,

Overview

Publisherahmed-lakosha
Repositoryodoo-plugins
Skill nameodoo-docker
Stars
74
Forks
33
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by ahmed-lakosha on GitHub. Read the source before you install it.

Installation

Install the Odoo Docker AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/ahmed-lakosha/odoo-plugins.git /tmp/odoo-plugins
mkdir -p .claude/skills
cp -r /tmp/odoo-plugins/odoo-docker-plugin/odoo-docker .claude/skills/odoo-docker
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Odoo Docker in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Odoo Docker on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Odoo Docker is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Odoo Docker Infrastructure Skill

1. Overview

Docker infrastructure and deployment expert for multi-version Odoo Enterprise environments. Handles production deployment, nginx configuration, CI/CD pipelines, performance tuning, security hardening, and container troubleshooting.

v2.1: Nginx config, debugging, and performance tuning are handled via natural language. For project init, compose generation, deployment, and builds, use /odoo-docker sub-commands.

What This Skill Does

  • Production Deployment: docker-compose with nginx, SSL, PostgreSQL tuning, resource limits, warm-up
  • CI/CD Pipelines: Build and push multi-version Docker images via GitHub Actions
  • Performance Tuning: Data-driven recommendations from real stress tests
  • Nginx Configuration: Optimized configs with gzip (90% CSS reduction), WebSocket, asset caching
  • Container Debugging: Systematic troubleshooting using known issue patterns
  • Project Setup: Auto-detect Odoo version, scan modules, generate all configs + IDE integration
  • Compose Generation: Smart compose for dev/staging/production scenarios
  • Image Management: Build, tag, push images for Odoo 14-19 (amd64 + arm64)

When to Use This Skill vs odoo-service

Use odoo-service for...Use odoo-docker for...
Starting/stopping serversDeploying to production
Basic docker up/down/logsConfiguring nginx reverse proxy
Database backup/restoreCI/CD pipeline setup
IDE configurationPerformance analysis & tuning
Environment initializationContainer debugging & troubleshooting
Module install/updateBuilding & pushing Docker images

Natural Language Triggers

  • "deploy to production", "production docker setup", "deploy odoo with nginx"
  • "configure nginx for odoo", "add reverse proxy", "enable gzip"
  • "optimize docker performance", "slow containers", "tune workers"
  • "build docker image", "push to docker hub", "ci/cd pipeline"
  • "container won't start", "500 errors in docker", "debug container"
  • "set up docker for this project", "initialize docker environment"
  • "generate docker-compose", "create compose file"

2. User Configuration

Users can customize this plugin by creating ~/.claude/odoo-docker.local.md with YAML frontmatter. See odoo-docker.local.md.example in the plugin root for the full template.

Key settings:

  • image_prefix: Docker Hub org/image prefix (default: myorg/odoo)
  • default_version: Default Odoo version when not auto-detected (default: 17)
  • git_org: GitHub organization for source clone suggestions

When generating configs, check for user overrides in .local.md first. If not found, use template defaults and prompt the user for their image prefix on first use.


3. Architecture

Core Principle: Source Mounted, Not Baked

Docker Hub:  {image_prefix}:19.0-enterprise   (pre-built base image)

Workspace:
  sources/odoo-19/          <-- Odoo Enterprise source (git clone, mounted read-only)
  projects/relief_center/   <-- Custom modules (git clone, mounted)
  compose/relief_center.yml <-- Per-project Docker Compose
  conf/relief_center.conf   <-- Per-project Odoo config

One image --> Many containers. No rebuilding per project.

Key Design Decisions

  1. Source code is NOT baked into the image — mounted at runtime via Docker volumes (read-only)
  2. Two deployment models: Standalone workspaces (per-version Dockerfile) and centralized workspace (pre-built images from Docker Hub)
  3. Container isolation: Each project gets its own Docker network, named volumes, port mappings

Container Directory Structure

/opt/odoo/source/           <-- Odoo source (mounted, read-only)
/opt/odoo/custom-addons/    <-- Custom modules (mounted)
/etc/odoo/odoo.conf         <-- Configuration (mounted, read-only)
/var/log/odoo/              <-- Log files (mounted)
/var/lib/odoo/              <-- Filestore + compiled assets (named volume)

Exposed Ports

PortPurpose
8069HTTP — Odoo web interface
8072Gevent/Longpolling — WebSocket, live chat, bus
5678Remote debugger (debugpy, optional)

4. Template Files

All templates are in ${CLAUDE_PLUGIN_ROOT}/templates/. Read them with the Read tool when generating configs.

TemplateUse ForKey Placeholders
docker-compose.dev.ymlDevelopment compose{postgres_image}, {version}, {project_name}
docker-compose.prod.ymlProduction compose with nginx+ {odoo_image}
Dockerfile.templateBuilding base imagesPYTHON_VERSION, ODOO_VERSION (build args)
nginx.confReverse proxy{server_name}
entrypoint.shContainer startup scriptEnvironment variables (see section 7)
odoo.conf.templateOdoo configuration{project_name}, {addons_paths}, {gevent_or_longpolling_key}, {admin_password}
.env.templateEnvironment variablesCopy and customize

Placeholder Convention

  • {placeholder} — Must be replaced by the user/skill before use
  • ${ENV_VAR:-default} — Resolved automatically by Docker Compose at runtime

5. Version Matrix

Full version matrix is in ${CLAUDE_PLUGIN_ROOT}/reference/version-matrix.md. Key lookup table:

VersionPostgreSQLGevent KeyEntry PointPython
14-16postgres:12longpolling_portodoo-bin3.8-3.10
17postgres:15gevent_portodoo-bin3.10
18postgres:15gevent_portodoo-bin3.11
19postgres:15gevent_portsetup/odoo3.12

Build Workarounds (Applied Automatically)

VersionIssueFix
14Buster EOLarchive.debian.org mirrors
14-15gevent compilationCython<3, no-build-isolation
16-17gevent compilationCython<3, no-build-isolation
18cbor2 buildPIP_CONSTRAINT="setuptools<81"
19No __init__.pyPYTHONPATH=/opt/odoo/source
Allsetuptools 80+PIP_CONSTRAINT="setuptools<81"

6. Critical Configuration Notes

These are the most important settings. Getting any of them wrong causes hard-to-diagnose failures.

SettingWhy It Matters
data_dir = /var/lib/odooCRITICAL. Without this, filestore defaults to ~/.local/share/Odoo/ (ephemeral). JS assets return HTTP 500.
workers = 0Single-threaded. OK for dev. At 50 users: P50 = 10s, 10% errors. Minimum production: workers=2.
proxy_mode = TrueRequired behind nginx. Without it, IP logging and URL generation are wrong.
list_db = FalseProduction security. Prevents database name enumeration.
gevent_port vs longpolling_portv14-16: longpolling_port. v17+: gevent_port. Wrong key = WebSocket broken.
db_maxconn = 16Without limit, 51+ idle connections accumulate under stress. Pool exhaustion risk.

7. Environment Variables

Entrypoint Variables

VariableDefaultValuesPurpose
DEV_MODE00, 1Enables --dev=all for auto-reload
ENABLE_DEBUGGER00, 1Starts debugpy on port 5678, waits for IDE
WAIT_FOR_DB00, 1Waits up to 30s for PostgreSQL before starting
LOG_LEVEL(none)debug, info, warn, error, criticalOverrides odoo.conf log level
ODOO_EXTRA_ARGS(none)Any CLI argsPassed directly to Odoo CLI

Port Allocation Convention

PortCalculationProject 1Project 2
HTTPHTTP_PORT80698169
GeventHTTP_PORT + 380728172
DebugHTTP_PORT + 60986788778

8. Performance Tuning

Workers Configuration

SettingResponse at 50 UsersUse Case
workers=0P50 = 9,068ms, 10% errorsDev only
workers=2P50 ~ 800msMinimum production
workers=4P50 ~ 400msHeavy load

Formula: workers = (CPU cores * 2) + 1 (capped at available RAM / 512MB per worker)

PostgreSQL Tuning

SettingDefault4 GB RAM16 GB RAM
shared_buffers128 MB1 GB4 GB
work_mem4 MB16 MB32 MB
effective_cache_size4 GB3 GB12 GB
maintenance_work_mem64 MB128 MB512 MB
random_page_cost4.01.11.1

Gzip Compression (Nginx)

ConfigurationCSS SizeReduction
Dev (Werkzeug, no gzip)894 KB
Prod (nginx, gzip level 6)89 KB90%

Asset Warm-Up

First request after restart compiles all assets (25-120s). The production compose template includes a warm-up service that pre-loads /web/login and /shop.


9. Security Hardening

High-Risk Issues (Fix Before Production)

IssueDefaultFix
Database enumerationlist_db = Truelist_db = False
Weak master passwordadmin_passwd = 123Strong 32+ character password
No SSL/TLSPlaintext HTTPNginx + Let's Encrypt
Default DB credentialsodoo / odooCustom credentials per environment
Proxy mode disabledproxy_mode = Falseproxy_mode = True behind nginx

Volume Security

  • Odoo source: Always mount :ro (read-only)
  • Config files: Always mount :ro
  • Filestore and logs: Read-write (necessary for operation)

Network Isolation

  • Each project gets its own Docker network
  • Database containers are NOT exposed to host in production
  • Only nginx exposes ports to the outside

10. SSL/TLS Configuration

For production HTTPS, the nginx template (${CLAUDE_PLUGIN_ROOT}/templates/nginx.conf) has commented SSL blocks. Uncomment and configure:

nginx
server {
    listen 80;
    server_name yourdomain.com;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl http2;
    server_name yourdomain.com;
    ssl_certificate /etc/letsencrypt/live/yourdomain.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/yourdomain.com/privkey.pem;
    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_ciphers HIGH:!aNULL:!MD5;
    ssl_prefer_server_ciphers on;
    # ... (same location blocks as HTTP config)
}

Add Let's Encrypt volume to production compose:

yaml
nginx:
  volumes:
    - /etc/letsencrypt:/etc/letsencrypt:ro
  ports:
    - "443:443"

11. CI/CD Pipeline

GitHub Actions Overview

  • Triggers: Push to main (Dockerfile/entrypoint/requirements changes) or manual dispatch
  • Matrix: Builds all 6 versions in parallel
  • Multi-platform: linux/amd64 + linux/arm64
  • Cache: GitHub Actions layer cache per version
  • Tags: {image_prefix}:{version}.0-enterprise + SHA suffix

Required Secrets

SecretPurpose
DOCKERHUB_USERNAMEDocker Hub login
DOCKERHUB_TOKENDocker Hub access token

The full GitHub Actions workflow template is generated by /odoo-docker build --generate-ci.


12. Centralized Multi-Project Workspace

Layout

~/odoo-docker/
├── sources/         <-- Git clones of Odoo Enterprise (per version)
├── projects/        <-- Git clones of custom modules (per project)
├── conf/            <-- Generated Odoo configs
├── compose/         <-- Generated Docker Compose files
├── logs/            <-- Runtime logs
├── scripts/         <-- start.sh, stop.sh, logs.sh, shell.sh
├── .env             <-- Global config
└── .env.local       <-- Machine-specific overrides

Daily Commands

bash
./scripts/start.sh <project>            # Start containers
./scripts/start.sh <project> --dev      # Start with auto-reload
./scripts/stop.sh <project>             # Stop containers
./scripts/logs.sh <project>             # Odoo logs
./scripts/shell.sh <project> 19         # Bash into container

Running Multiple Projects

Assign unique ports per project in .env:

env
RELIEF_CENTER_HTTP_PORT=8069
SOQYA_HTTP_PORT=8169
TAQAT_HTTP_PORT=8269

13. Database Management in Docker

Create Database via API

bash
curl -s -X POST http://localhost:8069/web/database/create \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"call","params":{"master_pwd":"changeme","name":"my_db","lang":"en_US","password":"admin","login":"admin"}}'

Access from Host

bash
psql -h localhost -p 5433 -U odoo -d my_database

Backup and Restore

bash
docker exec {db_container} pg_dump -U odoo my_database > backup.sql
docker exec -i {db_container} psql -U odoo -d my_database < backup.sql

14. Debugging & Development

Dev Mode

bash
DEV_MODE=1 docker compose up -d

Remote Debugger (debugpy)

  1. Set ENABLE_DEBUGGER=1 in .env
  2. Expose port 5678:5678 in docker-compose
  3. Container waits for IDE attach
  4. VS Code config:
json
{
  "name": "Attach to Odoo Docker",
  "type": "debugpy",
  "request": "attach",
  "connect": { "host": "localhost", "port": 5678 },
  "pathMappings": [
    { "localRoot": "${workspaceFolder}", "remoteRoot": "/opt/odoo/source" }
  ]
}

Module Management Inside Container

bash
python -m odoo -c /etc/odoo/odoo.conf -d {db} -u {module} --stop-after-init
python -m odoo -c /etc/odoo/odoo.conf -d {db} -i {module} --stop-after-init

15. Troubleshooting

For the full troubleshooting reference with all known issue patterns and diagnostic commands, read ${CLAUDE_PLUGIN_ROOT}/reference/troubleshooting.md.

For performance-related patterns and lessons learned from stress tests, read ${CLAUDE_PLUGIN_ROOT}/reference/docker-patterns.md.

For the production deployment checklist, read ${CLAUDE_PLUGIN_ROOT}/reference/production-checklist.md.


16. Quick Command Reference

bash
# Build local image
docker compose build

# Pull pre-built image
docker pull {image_prefix}:19.0-enterprise

# Start / Stop
docker compose up -d
docker compose down

# Logs / Shell
docker compose logs -f odoo
docker compose exec odoo bash

# Module update inside container
python -m odoo -c /etc/odoo/odoo.conf -d {db} -u {module} --stop-after-init

Frequently asked questions

What does the Odoo Docker AI skill do?

Docker infrastructure manager for Odoo — production deployment, nginx proxy, CI/CD pipelines, performance tuning, multi-version image management, container debugging, and centralized workspace orchestration for Odoo 14-19 Enterprise. v2.0 consolidates nginx, debug, and perf into natural language triggers alongside the /odoo-docker sub-command interface. <example> Context: User wants to deploy Odoo to production with Docker user: "Deploy my Odoo 17 project to production using Docker" assistant: "I will use the odoo-docker skill to generate a production docker-compose.yml with Odoo, PostgreSQ...

Why use Odoo Docker on TypingMind?

Because you install it once and use it with any model. Odoo Docker is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Odoo Docker in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ahmed-lakosha/odoo-plugins/tree/master/odoo-docker-plugin/odoo-docker. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Odoo Docker?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Odoo Docker?

As many as you like. As long as a model supports skills, you can use Odoo Docker with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Odoo Docker AI skill free?

Yes. It is published on GitHub by ahmed-lakosha under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇