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

[bitnami/odoo] Release 19.0.20260501-debian-12-r0 (#92724)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-05-01 10:12:03 +02:00
committed by GitHub
parent 3ea4edd82e
commit 9521a15e65
2 changed files with 15 additions and 74 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/odoo/19/debian-12/Dockerfile
+7 -7
View File
@@ -7,13 +7,13 @@ 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-04-08T21:57:19Z" \
org.opencontainers.image.created="2026-05-01T07:24:23Z" \
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" \
org.opencontainers.image.title="odoo" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="19.0.20260401"
org.opencontainers.image.version="19.0.20260501"
ENV OS_ARCH="${TARGETARCH:-amd64}" \
OS_FLAVOUR="debian-12" \
@@ -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.13-3-linux-${OS_ARCH}-debian-12" \
"python-3.12.13-7-linux-${OS_ARCH}-debian-12" \
"render-template-1.0.9-164-linux-${OS_ARCH}-debian-12" \
"postgresql-client-18.3.0-0-linux-${OS_ARCH}-debian-12" \
"node-22.22.2-0-linux-${OS_ARCH}-debian-12" \
"odoo-19.0.20260401-0-linux-${OS_ARCH}-debian-12" \
"node-22.22.2-1-linux-${OS_ARCH}-debian-12" \
"odoo-19.0.20260501-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -56,9 +56,9 @@ RUN curl -sLO "https://github.com/wkhtmltopdf/packaging/releases/download/0.12.6
COPY rootfs /
RUN /opt/bitnami/scripts/odoo/postunpack.sh
ENV APP_VERSION="19.0.20260401" \
ENV APP_VERSION="19.0.20260501" \
BITNAMI_APP_NAME="odoo" \
IMAGE_REVISION="1" \
IMAGE_REVISION="0" \
LD_LIBRARY_PATH="/opt/bitnami/postgresql/lib:$LD_LIBRARY_PATH" \
PATH="/opt/bitnami/python/bin:/opt/bitnami/common/bin:/opt/bitnami/postgresql/bin:/opt/bitnami/node/bin:/opt/bitnami/odoo/bin:$PATH"
bitnami/odoo/README.md
+8 -67
View File
@@ -11,7 +11,13 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
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](#environment-variables) section for a more secure deployment.
## Using `docker-compose.yml`
The docker-compose.yaml file of this container can be found in the [Bitnami Containers repository](https://github.com/bitnami/containers/).
[https://github.com/bitnami/containers/tree/main/bitnami/odoo/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/odoo/docker-compose.yml)
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).
## Why use Bitnami Secure Images?
@@ -115,8 +121,6 @@ The following tables list the main variables you can set.
| `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
@@ -135,70 +139,7 @@ The Bitnami Odoo Docker image from the [Bitnami Secure Images](https://go-vmware
## Logging
The Bitnami Odoo Docker image sends the container logs to `stdout`. To view the logs:
```console
docker logs odoo
```
Or using Docker Compose:
```console
docker-compose logs odoo
```
You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) 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
```console
docker stop odoo
```
Or using Docker Compose:
```console
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.
```console
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:
```diff
$ 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:
```diff
$ docker run -d --name odoo \
...
- --volume /path/to/odoo-persistence:/bitnami/odoo \
+ --volume /path/to/odoo-backups/latest:/bitnami/odoo \
bitnami/odoo:latest
```
The Bitnami Odoo Docker image sends the container logs to the `stdout`. You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
## Notable Changes