Odoo is a suite of web based open source business apps. Odoo Apps can be used as stand-alone applications, but they also integrate seamlessly so you get a full-featured Open Source ERP when you install several Apps.
$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-odoo/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d
- Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
- With Bitnami images the latest bug fixes and features are available as soon as possible.
- Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
- All our images are based on minideb a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading linux distribution.
- Bitnami container images are released daily with the latest distribution packages available.
The image overview badge contains a security report with all open CVEs. Click on 'Show only CVEs with fixes' to get the list of actionable security issues.
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.
Bitnami containers can be used with Kubeapps for deployment and management of Helm Charts in clusters.
NOTE: Debian 8 images have been deprecated in favor of Debian 9 images. Bitnami will not longer publish new Docker images based on Debian 8.
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.
11-ol-7
,11.0.20181215-ol-7-r4
(11/ol-7/Dockerfile)11-debian-9
,11.0.20181215-debian-9-r2
,11
,11.0.20181215
,11.0.20181215-r2
,latest
(11/debian-9/Dockerfile)
Subscribe to project updates by watching the bitnami/odoo GitHub repo.
To run this application you need Docker Engine 1.10.0. Docker Compose is recomended with a version 1.6.0 or later.
Running Odoo with a database server is the recommended way. You can either use docker-compose or run the containers manually.
This is the recommended way to run Odoo. You can use the following docker compose template:
version: '2'
services:
postgresql:
image: 'bitnami/postgresql:latest'
volumes:
- 'postgresql_data:/bitnami'
odoo:
image: 'bitnami/odoo:latest'
ports:
- '80:8069'
- '443:8071'
volumes:
- 'odoo_data:/bitnami'
depends_on:
- postgresql
volumes:
postgresql_data:
driver: local
odoo_data:
driver: local
If you want to run the application manually instead of using docker-compose, these are the basic steps you need to run:
- Create a new network for the application and the database:
$ docker network create odoo-tier
- Start a PostgreSQL database in the network generated:
$ docker run -d --name postgresql --net odoo-tier bitnami/postgresql:latest
Note: You need to give the container a name in order to Odoo to resolve the host
- Run the Odoo container:
$ docker run -d -p 80:8069 -p 443:8071 --name odoo --net odoo-tier bitnami/odoo:latest
Then you can access your application at http://your-ip/
If you remove the container all your data and configurations will be lost, and the next time you run the image the application 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 volume at the /bitnami
path. Additionally you should mount a volume for persistence of the PostgreSQL data.
The above examples define docker volumes namely postgresql_data
and odoo_data
. The Odoo application state will persist as long as these volumes are not removed.
To avoid inadvertent removal of these volumes you can mount host directories as data volumes. Alternatively you can make use of volume plugins to host the volume data.
This requires a minor change to the docker-compose.yml
template previously shown:
version: '2'
services:
postgresql:
image: 'bitnami/postgresql:latest'
volumes:
- '/path/to/postgresql_persistence:/bitnami'
odoo:
image: bitnami/odoo:latest
depends_on:
- postgresql
ports:
- 80:8069
- 443:8071
volumes:
- '/path/to/odoo-persistence:/bitnami'
In this case you need to specify the directories to mount on the run command. The process is the same than the one previously shown:
- Create a network (if it does not exist):
$ docker network create odoo-tier
- Create a PostgreSQL container with host volume:
$ docker run -d --name postgresql \
--net odoo-tier \
--volume /path/to/postgresql-persistence:/bitnami \
bitnami/postgresql:latest
Note: You need to give the container a name in order to Odoo to resolve the host
- Create the Odoo container with hist volumes:
$ docker run -d --name odoo -p 80:8069 -p 443:8071 \
--net odoo-tier \
--volume /path/to/odoo-persistence:/bitnami \
bitnami/odoo:latest
Bitnami provides up-to-date versions of PostgreSQL and Odoo, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container. We will cover here the upgrade of the Odoo container. For the PostgreSQL upgrade see https://github.com/bitnami/bitnami-docker-postgresql/blob/master/README.md#upgrade-this-image
- Get the updated images:
$ docker pull bitnami/odoo:latest
- Stop your container
- For docker-compose:
$ docker-compose stop odoo
- For manual execution:
$ docker stop odoo
- Take a snapshot of the application state
$ rsync -a /path/to/odoo-persistence /path/to/odoo-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)
Additionally, snapshot the PostgreSQL data
You can use these snapshots to restore the application state should the upgrade fail.
- Remove the stopped container
- For docker-compose:
$ docker-compose rm odoo
- For manual execution:
$ docker rm odoo
- Run the new image
- For docker-compose:
$ docker-compose up odoo
- For manual execution (mount the directories if needed):
docker run --name odoo bitnami/odoo:latest
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. If you want to add a new environment variable:
- For docker-compose add the variable name and value under the application section:
odoo:
image: bitnami/odoo:latest
ports:
- 80:8069
- 443:8071
environment:
- ODOO_PASSWORD=my_password
volumes:
- 'odoo_data:/bitnami'
depends_on:
- postgresql
- For manual execution add a
-e
option with each variable and value:
$ docker run -d -p 80:8069 -p 443:8071 --name odoo \
--env ODOO_PASSWORD=my_password \
--net odoo-tier \
--volume /path/to/odoo-persistence:/bitnami \
bitnami/odoo:latest
Available variables:
ODOO_EMAIL
: Odoo application email. Default: user@example.comODOO_PASSWORD
: Odoo application password. Default: bitnamiPOSTGRESQL_USER
: Root user for the PostgreSQL database. Default: postgresPOSTGRESQL_PASSWORD
: Root password for the PostgreSQL.POSTGRESQL_HOST
: Hostname for PostgreSQL server. Default: postgresqlPOSTGRESQL_PORT_NUMBER
: Port used by PostgreSQL server. Default: 5432
To configure Odoo to send email using SMTP you can set the following environment variables:
SMTP_HOST
: SMTP host.SMTP_PORT
: SMTP port.SMTP_USER
: SMTP account user.SMTP_PASSWORD
: SMTP account password.SMTP_TLS
: Use TLS encription with SMTP. Default true
This would be an example of SMTP configuration using a GMail account:
- docker-compose:
odoo:
image: bitnami/odoo:latest
ports:
- 80:8069
- 443:8071
environment:
- SMTP_HOST=smtp.gmail.com
- SMTP_PORT=587
- SMTP_USER=your_email@gmail.com
- SMTP_PASSWORD=your_password
- For manual execution:
$ docker run -d -p 80:8069 -p 443:8071 --name odoo \
--env SMTP_HOST=smtp.gmail.com \
--env SMTP_PORT=587 \
--env SMTP_USER=your_email@gmail.com \
--env SMTP_PASSWORD=your_password \
--net odoo-tier \
--volume /path/to/odoo-persistence:/bitnami \
bitnami/odoo:latest
We'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.
If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:
- Host OS and version
- Docker version (
$ docker version
) - Output of
$ docker info
- Version of this container (
$ echo $BITNAMI_IMAGE_VERSION
inside the container) - The command you used to run the container, and any relevant output you saw (masking any sensitive information)
Copyright 2016-2018 Bitnami
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.