Public | Automated Build

Last pushed: a day ago
Short Description
Official image for biboumi, the XMPP <-> IRC gateway.
Full Description

Biboumi Docker Image


This image does not embed any XMPP server. You need to have a running XMPP server first: as an other docker image, or running on the host machine.

Assuming you have a running prosody container already running and properly configured you can use the following command to start your biboumi container.

docker run --link prosody:xmpp \
    -v $PWD/database:/var/lib/biboumi \
    -e \
    -e BIBOUMI_ADMIN=blabla \

If instead you already have an XMPP server running on the host machine, you can start the biboumi container like this:

docker run --network=host \
    -v $PWD/database:/var/lib/biboumi \
    -e \
    -e BIBOUMI_ADMIN=blabla \


The configuration file inside the image contains only a few default values. To be able to run, biboumi needs additional configuration. Additional options can be passed using environment variables. Any configuration option can be customized this way (see biboumi’s doc), but the main are listed here for convenience:

  • BIBOUMI_HOSTNAME: Sets the value of the hostname option.
  • BIBOUMI_PASSWORD: Sets the value of the password option.
  • BIBOUMI_ADMIN: Sets the value of the admin option.
  • BIBOUMI_XMPP_SERVER_IP: Sets the value of the xmpp_server_ip option. The default value is xmpp.
  • BIBOUMI_DB_NAME: Sets the database name to be used by biboumi: a filesystem path pointing at a Sqlite3 file, or a postgresql URI (starting with “postgresql://”). See below to learn how to mount a host directory (to save your Sqlite3 database) or how to link with a postgresql docker container.

You can also directly provide your own configuration file by mounting it inside the container using the -v option:

docker run --link prosody:xmpp \
    -v $PWD/biboumi.cfg:/etc/biboumi/biboumi.cfg \

If both a custom configuration file and custom environment variables are passed to the container, the environment variables will take precedence.

Linking with the XMPP server

You can use the --link option to connect to any server running in a docker container, but it needs to be called xmpp, or the custom value set for the BIBOUMI_XMPP_SERVER_IP option. For example, if you are using a container named ejabberd, you would use the option --link ejabberd:xmpp.

If you want to connect to the XMPP server running on the host machine, use the --network=host option.


By default, a sqlite3 database is stored in the /var/lib/biboumi/ directory. If you don’t bind a local directory to it, the database will be lost when the container is stopped. If you want to keep your database between each run, bind it with the -v option, like this: -v /srv/biboumi/:/var/lib/biboumi.

Note: Due to a limitation in Docker, to be able to read and write into this database, make sure this mounted directory has the proper read and write permissions on the host: it can be owned by UID and GID 1000:1000, or use chmod to give permissions to everyone, for example.

chown -R 1000:1000 database/
chmod 777 database/

Linking with a PostgreSQL container

If you want to use a PostgreSQL database, you need to either access the host database (run the biboumi container with --network=host), or link with a postgresql docker image.

To do that, start the PostgreSQL container like this:

docker run --name postgres postgres:latest

This will run a postgresql instance with a configured superuser named “postgres”, with no password and a database named “postgres” as well. If you want different values, please refer to the PostgreSQL’s image documentation.

Then start your biboumi container, by linking with this PostgreSQL container, and by specifying the correct db_name value (of course, also specify all the other options, like the XMPP hostname and password):

docker run --name biboumi \
    --link=postgres \
    -e BIBOUMI_DB_NAME=postgres://postgres@postgres/postgres \
Docker Pull Command
Source Repository