This Dockerfile is intended to be used to set up a standalone RabbitMQ queue broker, as well as a base image to set up a cluster with high availability queue support by default (Mirrored queues).
By default, the RabbitMQ broker is started as single node. If you want to start a cluster, you need to use the
rabbitmq-cluster Docker image, based on
rabbitmq image plus the
- 3.10 Dockerfile (Security Support until July 2023) -
This image is prepared to be used on Lagoon. There are therefore some things already done:
- Folder permissions are automatically adapted with
fix-permissions, so this image will work with a random user.
- The file
/etc/rabbitmq/definitions.jsonis parsed through
envplatewith a container-entrypoint.
Included RabbitMQ default schema (definitions.json)#
- To enable the support for Mirrored Queues, at least one
definitions.jsonschema file, minimal entities are defined to make the
passwordto access management
By default, a policy called
lagoon-ha is created at startup, but it is not active because it doesn't match any queue's name pattern (see default Environment Variables).
By default, the
ha-mode is set to
exactly which controls the exact number of mirroring nodes for a queue (mirrors). The number of nodes is controller by
For further information and custom configuration, please refer to official RabbitMQ documentation.
Some options are configurable via environment variables.
|Username for management UI access.
|Password for management UI access.
|RabbitMQ main virtualhost.
|Regular expression to match for mirrored queues.