public_git/bitnami-containers
1
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-10-17 17:40:47 +02:00
Code Issues Projects Releases Wiki Activity

[bitnami/odoo] Release 19.0.20260201-debian-12-r4 (#91065)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-02-24 13:47:36 +01:00
committed by GitHub
parent 432b398d39
commit e707ccb547
2 changed files with 8 additions and 221 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/odoo/19/debian-12/Dockerfile
+4 -4
View File
@@ -7,7 +7,7 @@ ARG DOWNLOADS_URL="downloads.bitnami.com/files/stacksmith"
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
org.opencontainers.image.created="2026-02-18T12:41:52Z" \
org.opencontainers.image.created="2026-02-24T12:01:36Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/odoo/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/odoo" \
@@ -27,11 +27,11 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
DOWNLOADS_URL=${SECRET_DOWNLOADS_URL:-${DOWNLOADS_URL}} ; \
mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
COMPONENTS=( \
"python-3.12.12-16-linux-${OS_ARCH}-debian-12" \
"python-3.12.12-19-linux-${OS_ARCH}-debian-12" \
"render-template-1.0.9-162-linux-${OS_ARCH}-debian-12" \
"postgresql-client-18.2.0-0-linux-${OS_ARCH}-debian-12" \
"node-22.22.0-1-linux-${OS_ARCH}-debian-12" \
"odoo-19.0.20260201-0-linux-${OS_ARCH}-debian-12" \
"odoo-19.0.20260201-1-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -58,7 +58,7 @@ COPY rootfs /
RUN /opt/bitnami/scripts/odoo/postunpack.sh
ENV APP_VERSION="19.0.20260201" \
BITNAMI_APP_NAME="odoo" \
IMAGE_REVISION="3" \
IMAGE_REVISION="4" \
PATH="/opt/bitnami/python/bin:/opt/bitnami/common/bin:/opt/bitnami/postgresql/bin:/opt/bitnami/node/bin:/opt/bitnami/odoo/bin:$PATH"
EXPOSE 3000 8069 8072
bitnami/odoo/README.md
+4 -217
View File
@@ -68,52 +68,10 @@ docker build -t bitnami/APP:latest .
Odoo requires access to a PostgreSQL database to store information. We'll use the [Bitnami Docker Image for PostgreSQL](https://github.com/bitnami/containers/tree/main/bitnami/postgresql) for the database requirements.
### Using the Docker Command Line
#### Step 1: Create a network
```console
docker network create odoo-network
```
#### Step 2: Create a volume for PostgreSQL persistence and create a PostgreSQL container
```console
$ docker volume create --name postgresql_data
docker run -d --name postgresql \
--env ALLOW_EMPTY_PASSWORD=yes \
--env POSTGRESQL_PASSWORD=bitnami \
--network odoo-network \
--volume postgresql_data:/bitnami/postgresql \
bitnami/postgresql:latest
```
#### Step 3: Create volumes for Odoo persistence and launch the container
```console
$ docker volume create --name odoo_data
docker run -d --name odoo \
-p 80:8069 \
--env ALLOW_EMPTY_PASSWORD=yes \
--env ODOO_DATABASE_ADMIN_PASSWORD=bitnami \
--network odoo-network \
--volume odoo_data:/bitnami/odoo \
bitnami/odoo:latest
```
Access your application at `http://your-ip/`
### Run the application using Docker Compose
```console
curl -sSL https://raw.githubusercontent.com/bitnami/containers/main/bitnami/odoo/docker-compose.yml > docker-compose.yml
docker-compose up -d
```
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](https://github.com/bitnami/charts/tree/main/bitnami/odoo).
If you detect any issue in the `docker-compose.yaml` file, feel free to report it or contribute with a fix by following our [Contributing Guidelines](https://github.com/bitnami/containers/blob/main/CONTRIBUTING.md).
## 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.
@@ -124,63 +82,8 @@ The above examples define the Docker volumes named `postgresql_data` and `odoo_d
To avoid inadvertent removal of volumes, you can [mount host directories as data volumes](https://docs.docker.com/engine/tutorials/dockervolumes/). Alternatively you can make use of volume plugins to host the volume data.
### Mount host directories as data volumes with Docker Compose
This requires a minor change to the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/odoo/docker-compose.yml) file present in this repository:
```diff
postgresql:
...
volumes:
- - postgresql_data:/bitnami/postgresql
+ - /path/to/postgresql-persistence:/bitnami/postgresql
...
odoo:
...
volumes:
- - odoo_data:/bitnami/odoo
+ - /path/to/odoo-persistence:/bitnami/odoo
...
-volumes:
- postgresql_data:
- driver: local
- odoo_data:
- driver: local
```
> NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.
### Mount host directories as data volumes using the Docker command line
#### Step 1: Create a network (if it does not exist)
```console
docker network create odoo-network
```
#### Step 2. Create a PostgreSQL container with host volume
```console
docker run -d --name postgresql \
--env ALLOW_EMPTY_PASSWORD=yes \
--env POSTGRESQL_PASSWORD=bitnami \
--network odoo-network \
--volume /path/to/postgresql-persistence:/bitnami/postgresql \
bitnami/postgresql:latest
```
#### Step 3. Create the Odoo container with host volumes
```console
docker run -d --name odoo \
-p 80:8069 \
--env ALLOW_EMPTY_PASSWORD=yes \
--env ODOO_DATABASE_ADMIN_PASSWORD=bitnami \
--network odoo-network \
--volume /path/to/odoo-persistence:/bitnami/odoo \
bitnami/odoo:latest
```
## Configuration
### Environment variables
@@ -229,93 +132,17 @@ docker run -d --name 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. If you want to add a new environment variable:
- For docker-compose add the variable name and value under the application section in the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/odoo/docker-compose.yml) file present in this repository:
```yaml
odoo:
...
environment:
- ODOO_PASSWORD=my_password
...
```
- For manual execution add a `--env` option with each variable and value:
```console
$ docker run -d --name odoo -p 80:8069 \
--env ODOO_PASSWORD=my_password \
--network odoo-tier \
--volume /path/to/odoo-persistence:/bitnami \
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.
### Examples
#### SMTP configuration using a Gmail account
#### SMTP configuration
This would be an example of SMTP configuration using a Gmail account:
- Modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/odoo/docker-compose.yml) file present in this repository:
```yaml
odoo:
...
environment:
- ALLOW_EMPTY_PASSWORD=yes
- ODOO_SMTP_HOST=smtp.gmail.com
- ODOO_SMTP_PORT_NUMBER=587
- ODOO_SMTP_USER=your_email@gmail.com
- ODOO_SMTP_PASSWORD=your_password
...
```
- For manual execution:
```console
$ docker run -d --name odoo -p 80:8069 \
--env ODOO_SMTP_HOST=smtp.gmail.com \
--env ODOO_SMTP_PORT_NUMBER=587 \
--env ODOO_SMTP_USER=your_email@gmail.com \
--env ODOO_SMTP_PASSWORD=your_password \
--network odoo-tier \
--volume /path/to/odoo-persistence:/bitnami \
bitnami/odoo:latest
```
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. This would be an example of using an external database for Odoo.
- Modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/odoo/docker-compose.yml) file present in this repository:
```diff
odoo:
...
environment:
- - ODOO_DATABASE_HOST=mariadb
+ - ODOO_DATABASE_HOST=mariadb_host
- ODOO_DATABASE_PORT_NUMBER=3306
- - ALLOW_EMPTY_PASSWORD=yes
+ - ODOO_DATABASE_ADMIN_PASSWORD=odoo_password
...
```
- For manual execution:
```console
$ docker run -d --name odoo\
-p 80:8069 \
--network odoo-network \
--env ODOO_DATABASE_HOST=mariadb_host \
--env ODOO_DATABASE_PORT_NUMBER=3306 \
--env ODOO_DATABASE_ADMIN_PASSWORD=odoo_password \
--volume odoo_data:/bitnami/odoo \
bitnami/odoo:latest
```
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.
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
@@ -390,46 +217,6 @@ For the Odoo container:
bitnami/odoo:latest
```
### Upgrade this image
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/containers/tree/main/bitnami/odoo#user-content-upgrade-this-image>
The `bitnami/odoo:latest` tag always points to the most recent release. To get the most recent release you can simple repull the `latest` tag from the Docker Hub with `docker pull bitnami/odoo:latest`. However it is recommended to use [tagged versions](https://hub.docker.com/r/bitnami/odoo/tags/).
#### Step 1: Get the updated image
```console
docker pull bitnami/odoo:latest
```
#### Step 2: Stop the running container
Stop the currently running container using the command
```console
docker-compose stop odoo
```
#### Step 3: Take a snapshot of the application state
Follow the steps in [Backing up your container](#backing-up-your-container) to take a snapshot of the current application state.
#### Step 4: Remove the currently running container
Remove the currently running container by executing the following command:
```console
docker-compose rm -v odoo
```
#### Step 5: Run the new image
Update the image tag in `docker-compose.yml` and re-create your container with the new image:
```console
docker-compose up -d
```
## Notable Changes
### 12.0.20210615-debian-10-r20, 13.0.20210610-debian-10-r24 and 14.0.20210610-debian-10-r22