ibeltechnology/ibel repository overview

⁠Quick reference

• Maintained by:
  Ibel technology⁠

• Where to get help:
  the Docker Community Forums⁠, the Docker Community Slack⁠, or Stack Overflow⁠

⁠Supported tags and respective Dockerfile links

• 14.0, 14, latest⁠

⁠Quick reference (cont.)

• Where to file issues:
  https://github.com/odoo/docker/issues⁠

• Supported architectures: (more info⁠)
  amd64⁠

⁠What is Ibel?

⁠

ibel.app⁠

⁠How to use this image

This image requires a running PostgreSQL server.

⁠Start a PostgreSQL server

$ docker run -d -e POSTGRES_USER=odoo -e POSTGRES_PASSWORD=odoo -e POSTGRES_DB=postgres --name db postgres:13

⁠Start an Ibel instance

$ docker run -p 8069:8069 --name ibel --link db:db -t ibeltechnology/ibel

The alias of the container running Postgres must be db for Ibel to be able to connect to the Postgres server.

⁠Stop and restart an Ibel instance

$ docker stop ibel
$ docker start -a ibel

⁠Use named volumes to preserve data

When the Ibel container is created like described above, the ibel filestore is created inside the container. If the container is removed, the filestore is lost. The preferred way to prevent that is by using a Docker named volume⁠.

$ docker run -v odoo-data:/var/lib/odoo -d -p 8069:8069 --name ibel --link db:db -t ibeltechnology/ibel

With the above command, the volume named odoo-data will persist even if the container is removed and can be re-used by issuing the same command.

The path /var/lib/odoo used as the mount point of the volume must match the odoo data_dir in the config file or as CLI parameters.

Note that the same principle applies to the Postgresql container and a named volume can be used to preserve the database when the container is removed. So the database container could be started like this (before the odoo container):

$ docker run -d -v odoo-db:/var/lib/postgresql/data -e POSTGRES_USER=odoo -e POSTGRES_PASSWORD=odoo -e POSTGRES_DB=postgres --name db postgres:13

⁠Stop and restart a PostgreSQL server

When a PostgreSQL server is restarted, the Odoo instances linked to that server must be restarted as well because the server address has changed and the link is thus broken.

Restarting a PostgreSQL server does not affect the created databases.

⁠Run Ibel with a custom configuration

The default configuration file for the server (located at /etc/odoo/odoo.conf) can be overriden at startup using volumes. Suppose you have a custom configuration at /path/to/config/odoo.conf, then

$ docker run -v /path/to/config:/etc/odoo -p 8069:8069 --name ibel --link db:db -t ibeltechnology/ibel

Please use this configuration template⁠ to write your custom configuration as we already set some arguments for running Odoo inside a Docker container.

You can also directly specify Ibel arguments inline. Those arguments must be given after the keyword -- in the command-line, as follows

$ docker run -p 8069:8069 --name ibel --link db:db -t ibeltechnology/ibel -- --db-filter=odoo_db_.*

⁠Mount custom addons

You can mount your own Ibel addons within the Ibel container, at /mnt/extra-addons

$ docker run -v /path/to/addons:/mnt/extra-addons -p 8069:8069 --name ibel --link db:db -t ibeltechnology/ibel

⁠Run multiple Ibel instances

$ docker run -p 8070:8069 --name ibel2 --link db:db -t ibeltechnology/ibel
$ docker run -p 8071:8069 --name ibel3 --link db:db -t ibeltechnology/ibel

Please note that for plain use of mails and reports functionalities, when the host and container ports differ (e.g. 8070 and 8069), one has to set, in Ibel, Settings->Parameters->System Parameters (requires technical features), web.base.url to the container port (e.g. 127.0.0.1:8069).

⁠Environment Variables

Tweak these environment variables to easily connect to a postgres server:

• HOST: The address of the postgres server. If you used a postgres container, set to the name of the container. Defaults to db.
• PORT: The port the postgres server is listening to. Defaults to 5432.
• USER: The postgres role with which Odoo will connect. If you used a postgres container, set to the same value as POSTGRES_USER. Defaults to odoo.
• PASSWORD: The password of the postgres role with which Ibel will connect. If you used a postgres container, set to the same value as POSTGRES_PASSWORD. Defaults to odoo.

⁠Docker Compose examples

The simplest docker-compose.yml file would be:

version: '3.1'
services:
  web:
    image: ibeltechnology/ibel:14.0
    depends_on:
      - db
    ports:
      - "8069:8069"
  db:
    image: postgres:13
    environment:
      - POSTGRES_DB=postgres
      - POSTGRES_PASSWORD=odoo
      - POSTGRES_USER=odoo

If the default postgres credentials does not suit you, tweak the environment variables:

version: '3.1'
services:
  web:
    image: ibeltechnology/ibel:14.0
    depends_on:
      - mydb
    ports:
      - "8069:8069"
    environment:
    - HOST=mydb
    - USER=odoo
    - PASSWORD=myodoo
  mydb:
    image: postgres:13
    environment:
      - POSTGRES_DB=postgres
      - POSTGRES_PASSWORD=myodoo
      - POSTGRES_USER=odoo

Here's a last example showing you how to

• mount custom addons located in ./addons
• use a custom configuration file located in .config/odoo.conf
• use named volumes for the Odoo and postgres data dir
• use a secrets file named odoo_pg_pass that contains the postgreql password shared by both services

version: '3.1'
services:
  web:
    image: ibeltechnology/ibel:14.0
    depends_on:
      - db
    ports:
      - "8069:8069"
    volumes:
      - odoo-web-data:/var/lib/odoo
      - ./config:/etc/odoo
      - ./addons:/mnt/extra-addons
    environment:
      - PASSWORD_FILE=/run/secrets/postgresql_password
    secrets:
      - postgresql_password
  db:
    image: postgres:13
    environment:
      - POSTGRES_DB=postgres
      - POSTGRES_PASSWORD_FILE=/run/secrets/postgresql_password
      - POSTGRES_USER=odoo
      - PGDATA=/var/lib/postgresql/data/pgdata
    volumes:
      - odoo-db-data:/var/lib/postgresql/data/pgdata
    secrets:
      - postgresql_password
volumes:
  odoo-web-data:
  odoo-db-data:

secrets:
  postgresql_password:
    file: odoo_pg_pass

To start your Ibel instance, go in the directory of the docker-compose.yml file you created from the previous examples and type:

docker-compose up -d

⁠How to upgrade this image

Ibel images are updated on a regular basis to make them use recent releases. Please be aware that what follows is about upgrading from an old release to the latest one provided of the same major version, as upgrading from a major version to another is a much more complex process requiring elaborated migration scripts (see this community project⁠ which aims to write those scripts).

Suppose you created a database from an Odoo instance named old-odoo, and you want to access this database from a new Ibel instance named new-ibel, e.g. because you've just downloaded a newer Ibel image.

By default, Ibel 14.0 uses a filestore (located at /var/lib/odoo/filestore/) for attachments. You should restore this filestore in your new Ibel instance by running

$ docker run --volumes-from old-ibel -p 8070:8069 --name new-ibel --link db:db -t ibeltechnology/ibel:14.0

You can also simply prevent Ibel from using the filestore by setting the system parameter ir_attachment.location to db-storage in Settings->Parameters->System Parameters (requires technical features).

⁠License

View license information⁠ for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

Some additional license information which was able to be auto-detected might be found in the repo-info repository's odoo/ directory⁠.

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.