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

[bitnami/odoo] Release 19.0.20260301-debian-12-r0 (#91199)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-03-02 19:14:41 +01:00
committed by GitHub
parent 56591ba9b8
commit a6bf1216a5
2 changed files with 30 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/odoo/19/debian-12/Dockerfile
+6 -6
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-02-25T09:53:40Z" \
org.opencontainers.image.created="2026-03-02T17:22:03Z" \
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.20260201"
org.opencontainers.image.version="19.0.20260301"
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.12-19-linux-${OS_ARCH}-debian-12" \
"python-3.12.12-23-linux-${OS_ARCH}-debian-12" \
"render-template-1.0.9-162-linux-${OS_ARCH}-debian-12" \
"postgresql-client-18.3.0-0-linux-${OS_ARCH}-debian-12" \
"node-22.22.0-1-linux-${OS_ARCH}-debian-12" \
"odoo-19.0.20260201-3-linux-${OS_ARCH}-debian-12" \
"odoo-19.0.20260301-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.20260201" \
ENV APP_VERSION="19.0.20260301" \
BITNAMI_APP_NAME="odoo" \
IMAGE_REVISION="6" \
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
+24 -22
View File
@@ -1,13 +1,11 @@
# Bitnami Secure Image for Odoo
## What is 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](https://www.odoo.com/)
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
## <a id="tl-dr"></a> TL;DR
```console
docker run --name odoo bitnami/odoo:latest
@@ -16,7 +14,7 @@ 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 d
eployment.
## Why use Bitnami Secure Images?
## <a id="why-use-bitnami-secure-images"></a> 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](https://vmware.github.io/photon/). Why choose BSI images?
@@ -33,16 +31,16 @@ Each image comes with valuable security metadata. You can view the metadata in [
If you are looking for our previous generation of images based on Debian Linux, please see the [Bitnami Legacy registry](https://hub.docker.com/u/bitnamilegacy).
## How to deploy Odoo in Kubernetes?
## <a id="how-to-deploy-in-kubernetes"></a> 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](https://github.com/bitnami/charts/tree/master/bitnami/odoo).
## Supported tags and respective `Dockerfile` links
## <a id="supported-tags"></a> 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](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html).
## Get this image
## <a id="get-this-image"></a> Get this image
The recommended way to get the Bitnami Odoo Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/odoo).
@@ -64,15 +62,15 @@ cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t bitnami/APP:latest .
```
## How to use this image
## <a id="how-to-use-this-image"></a> How to use this image
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.
### Run the application using Docker Compose
### <a id="run-the-application-using-docker-compose"></a> 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](https://github.com/bitnami/charts/tree/main/bitnami/odoo).
## Persisting your application
## <a id="persisting-your-application"></a> 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.
@@ -82,11 +80,15 @@ 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.
> NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.
> **NOTE** As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.
## Configuration
## <a id="configuration"></a> Configuration
### Environment variables
The following section describes the supported environment variables
### <a id="environment-variables"></a> Environment variables
The following tables list the main variables you can set.
#### Customizable environment variables
@@ -134,7 +136,7 @@ To avoid inadvertent removal of volumes, you can [mount host directories as data
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
### <a id="examples"></a> Examples
#### SMTP configuration
@@ -144,13 +146,13 @@ The `ODOO_SMTP_*` environment variables allows you configure the SMTP settings i
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
### <a id="fips-configuration"></a> FIPS configuration in Bitnami Secure Images
The Bitnami Odoo Docker image from the [Bitnami Secure Images](https://go-vmware.broadcom.com/contact-us) 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
## <a id="logging"></a> Logging
The Bitnami Odoo Docker image sends the container logs to `stdout`. To view the logs:
@@ -166,9 +168,9 @@ 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
## <a id="maintenance"></a> Maintenance
### Backing up your container
### <a id="backing-up-your-container"></a> Backing up your container
To backup your data, configuration and logs, follow these simple steps:
@@ -193,7 +195,7 @@ docker run --rm -v /path/to/odoo-backups:/backups --volumes-from odoo busybox \
cp -a /bitnami/odoo /backups/latest
```
### Restoring a backup
### <a id="restoring-a-backup"></a> Restoring a backup
Restoring a backup is as simple as mounting the backup as volumes in the containers.
@@ -217,9 +219,9 @@ For the Odoo container:
bitnami/odoo:latest
```
## Notable Changes
## <a id="notable-changes"></a> Notable Changes
### 12.0.20210615-debian-10-r20, 13.0.20210610-debian-10-r24 and 14.0.20210610-debian-10-r22
### <a id="12.0.20210615-debian-10-r20--13.0.20210610-debian-10-r24-and-14.0.20210610-debian-10-r22"></a> 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.
@@ -228,7 +230,7 @@ For the Odoo container:
- Added port 8072 to the list of exposed ports. This port is used by the [Odoo Longpolling service](https://www.odoo.com/documentation/14.0/administration/deployment/deploy.html#livechat).
- The `WITHOUT_DEMO` environment variable was deprecated in favor of the boolean `ODOO_LOAD_DEMO_DATA` environment variable.
## License
## <a id="license"></a> License
Copyright &copy; 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.