containers/bitnami/odoo

Bitnami Secure Image for Odoo

Odoo is an open source ERP and CRM platform, formerly known as OpenERP, that can connect a wide variety of business operations such as sales, supply chain, finance, and project management.

Overview of Odoo Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.

TL;DR

docker run --name odoo bitnami/odoo:latest

Warning: This quick setup is only intended for development environments. You are encouraged to change the insecure default credentials and check out the available configuration options in the Environment Variables section for a more secure deployment.

Why use Bitnami Secure Images?

Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise OS Photon Linux. Why choose BSI images?

• Hardened secure images of popular open source software with Near-Zero Vulnerabilities
• Vulnerability Triage & Prioritization with VEX Statements, KEV and EPSS Scores
• Compliance focus with FIPS, STIG, and air-gap options, including secure bill of materials (SBOM)
• Software supply chain provenance attestation through in-toto
• First class support for the internet’s favorite Helm charts

Each image comes with valuable security metadata. You can view the metadata in our public catalog here. Note: Some data is only available with commercial subscriptions to BSI.

If you are looking for our previous generation of images based on Debian Linux, please see the Bitnami Legacy registry.

How to deploy Odoo in Kubernetes?

Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the Bitnami Odoo Chart GitHub repository.

Supported tags and respective Dockerfile links

Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.

Get this image

The recommended way to get the Bitnami Odoo Docker Image is to pull the prebuilt image from the Docker Hub Registry.

docker pull bitnami/odoo:latest

To use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.

docker pull bitnami/odoo:[TAG]

If you wish, you can also build the image yourself by cloning the repository, changing to the directory containing the Dockerfile and executing the docker build command. Remember to replace the APP, VERSION and OPERATING-SYSTEM path placeholders in the example command below with the correct values.

git clone https://github.com/bitnami/containers.git
cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t bitnami/APP:latest .

How to use this image

Odoo requires access to a PostgreSQL database to store information. We'll use the Bitnami Docker Image for PostgreSQL for the database requirements.

Run the application using Docker Compose

Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated Bitnami Helm chart.

Persisting your application

If you remove the container all your data will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.

For persistence you should mount a directory at the /bitnami/odoo path. If the mounted directory is empty, it will be initialized on the first run. Additionally you should mount a volume for persistence of the PostgreSQL data.

The above examples define the Docker volumes named postgresql_data and odoo_data. The Odoo application state will persist as long as volumes are not removed.

To avoid inadvertent removal of volumes, you can mount host directories as data volumes. Alternatively you can make use of volume plugins to host the volume data.

Note

As this is a non-root container, the mounted files and directories must have the proper permissions for the UID 1001.

Configuration

The following section describes the supported environment variables

Environment variables

The following tables list the main variables you can set.

Customizable environment variables

Name	Description	Default Value
ODOO_DATA_TO_PERSIST	Files to persist relative to the Odoo installation directory. To provide multiple values, separate them with a whitespace.	${ODOO_ADDONS_DIR} ${ODOO_CONF_DIR} ${ODOO_DATA_DIR}
ODOO_PORT_NUMBER	Port number in which Odoo will run.	8069
ODOO_LONGPOLLING_PORT_NUMBER	Port number in which the Odoo Longpolling service will run.	8072
ODOO_SKIP_BOOTSTRAP	Whether to perform initial bootstrapping for the application.	no
ODOO_SKIP_MODULES_UPDATE	Whether to perform initial update of the plugins installed.	no
ODOO_LOAD_DEMO_DATA	Whether to load demo data.	no
ODOO_LIST_DB	Whether the database selector is available.	no
ODOO_EMAIL	Odoo user e-mail address.	user@example.com
ODOO_PASSWORD	Odoo user password.	bitnami
ODOO_SMTP_HOST	Odoo SMTP server host.	nil
ODOO_SMTP_PORT_NUMBER	Odoo SMTP server port number.	nil
ODOO_SMTP_USER	Odoo SMTP server user.	nil
ODOO_SMTP_PASSWORD	Odoo SMTP server user password.	nil
ODOO_SMTP_PROTOCOL	Odoo SMTP server protocol to use.	nil
ODOO_DATABASE_HOST	Database server host.	$ODOO_DEFAULT_DATABASE_HOST
ODOO_DATABASE_PORT_NUMBER	Database server port.	5432
ODOO_DATABASE_NAME	Database name.	bitnami_odoo
ODOO_DATABASE_USER	Database user name.	bn_odoo
ODOO_DATABASE_PASSWORD	Database user password.	nil
ODOO_DATABASE_FILTER	Database filter	nil

Read-only environment variables

Name	Description	Value
ODOO_BASE_DIR	Odoo installation directory.	${BITNAMI_ROOT_DIR}/odoo
ODOO_BIN_DIR	Odoo directory for binary executables.	${ODOO_BASE_DIR}/bin
ODOO_CONF_DIR	Odoo directory for configuration files.	${ODOO_BASE_DIR}/conf
ODOO_CONF_FILE	Configuration file for Odoo.	${ODOO_CONF_DIR}/odoo.conf
ODOO_DATA_DIR	Odoo directory for data files.	${ODOO_BASE_DIR}/data
ODOO_ADDONS_DIR	Odoo directory for extra addons.	${ODOO_ADDONS_DIR:-${ODOO_BASE_DIR}/addons}
ODOO_TMP_DIR	Odoo directory for temporary files.	${ODOO_BASE_DIR}/tmp
ODOO_PID_FILE	PID file for Odoo.	${ODOO_TMP_DIR}/odoo.pid
ODOO_LOGS_DIR	Odoo directory for log files.	${ODOO_BASE_DIR}/log
ODOO_LOG_FILE	Log file for Odoo.	${ODOO_LOGS_DIR}/odoo-server.log
ODOO_VOLUME_DIR	Odoo directory for mounted configuration files.	${BITNAMI_VOLUME_DIR}/odoo
ODOO_DAEMON_USER	Odoo system user.	odoo
ODOO_DAEMON_GROUP	Odoo system group.	odoo
ODOO_DEFAULT_DATABASE_HOST	Default database server host.	postgresql

When you start the Odoo image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the docker run command line.

Examples

SMTP configuration

The ODOO_SMTP_* environment variables allows you configure the SMTP settings in the application. Please take a look at the environment variables information above.

Connect Odoo container to an existing database

The Bitnami Odoo container supports connecting the Odoo application to an external database. In case the database already contains data from a previous Odoo installation, you need to set the variable ODOO_SKIP_BOOTSTRAP to yes. Otherwise, the container would execute the installation wizard and could modify the existing data in the database. Note that, when setting ODOO_SKIP_BOOTSTRAP to yes, values for environment variables such as ODOO_EMAIL or ODOO_PASSWORD will be ignored.

FIPS configuration in Bitnami Secure Images

The Bitnami Odoo Docker image from the Bitnami Secure Images catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables:

• OPENSSL_FIPS: whether OpenSSL runs in FIPS mode or not. yes (default), no.

Logging

The Bitnami Odoo Docker image sends the container logs to stdout. To view the logs:

docker logs odoo

Or using Docker Compose:

docker-compose logs odoo

You can configure the containers logging driver using the --log-driver option if you wish to consume the container logs differently. In the default configuration docker uses the json-file driver.

Maintenance

Backing up your container

To backup your data, configuration and logs, follow these simple steps:

Step 1: Stop the currently running container

docker stop odoo

Or using Docker Compose:

docker-compose stop odoo

Step 2: Run the backup command

We need to mount two volumes in a container we will use to create the backup: a directory on your host to store the backup in, and the volumes from the container we just stopped so we can access the data.

docker run --rm -v /path/to/odoo-backups:/backups --volumes-from odoo busybox \
  cp -a /bitnami/odoo /backups/latest

Restoring a backup

Restoring a backup is as simple as mounting the backup as volumes in the containers.

For the PostgreSQL database container:

 $ docker run -d --name postgresql \
   ...
-  --volume /path/to/postgresql-persistence:/bitnami/postgresql \
+  --volume /path/to/postgresql-backups/latest:/bitnami/postgresql \
   bitnami/postgresql:latest

For the Odoo container:

 $ docker run -d --name odoo \
   ...
-  --volume /path/to/odoo-persistence:/bitnami/odoo \
+  --volume /path/to/odoo-backups/latest:/bitnami/odoo \
   bitnami/odoo:latest

Notable Changes

12.0.20210615-debian-10-r20, 13.0.20210610-debian-10-r24 and 14.0.20210610-debian-10-r22

• The size of the container image has been decreased.
• The configuration logic is now based on Bash scripts in the rootfs/ folder.
• It is now possible to use an already populated Odoo database from another installation. In order to do this, use the environment variable ODOO_SKIP_BOOTSTRAP, which forces the container not to run the initial Odoo setup wizard.
• Removed port 8071 from list of exposed ports. This port was used by the Odoo XMLRPCS service, but was removed in Odoo 10.
• Added port 8072 to the list of exposed ports. This port is used by the Odoo Longpolling service.
• The WITHOUT_DEMO environment variable was deprecated in favor of the boolean ODOO_LOAD_DEMO_DATA environment variable.

License

Copyright © 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.