micdenny/rabbitmq-windows repository overview

⁠Supported tags and respective Dockerfile links

• 3.6.9⁠
• 3.6.12⁠
• 3.8.16⁠
• 3.8.35,3.8.35-servercore-ltsc2019,3.8.35-servercore-ltsc2022⁠
• 3.9.8⁠
• 3.9.22,3.9.22-servercore-ltsc2019,3.9.22-servercore-ltsc2022⁠
• 3.9.24,3.9.24-servercore-ltsc2019,3.9.24-servercore-ltsc2022⁠
• 3.9.29,3.9.29-servercore-ltsc2019,3.9.29-servercore-ltsc2022⁠
• 3.10.7,3.10.7-servercore-ltsc2019,3.10.7-servercore-ltsc2022⁠
• 3.10.10,3.10.10-servercore-ltsc2019,3.10.10-servercore-ltsc2022⁠
• 3.10.25,3.10.25-servercore-ltsc2019,3.10.25-servercore-ltsc2022⁠
• 3.11.2,3.11.2-servercore-ltsc2019,3.11.2-servercore-ltsc2022⁠
• 3.11.20,3.11.20-servercore-ltsc2019,3.11.20-servercore-ltsc2022⁠
• 3.12.2,3.12.2-servercore-ltsc2019,3.12.2-servercore-ltsc2022⁠
• 4.1.0,4.1.0-servercore-ltsc2019,4.1.0-servercore-ltsc2022⁠
• latest,ltsc2019-latest,ltsc2022-latest⁠

⁠What is RabbitMQ?

RabbitMQ is open source message broker software (sometimes called message-oriented middleware) that implements the Advanced Message Queuing Protocol (AMQP). The RabbitMQ server is written in the Erlang programming language and is built on the Open Telecom Platform framework for clustering and failover. Client libraries to interface with the broker are available for all major programming languages.

⁠How to use this image

⁠Running the daemon

One of the important things to note about RabbitMQ is that it stores data based on what it calls the "Node Name", which defaults to the hostname. What this means for usage in Docker is that we should specify -h/--hostname explicitly for each daemon so that we don't get a random hostname and can keep track of our data:

docker run -d --hostname my-rabbit --name some-rabbit micdenny/rabbitmq-windows

Specific version

docker run -d --hostname my-rabbit --name some-rabbit1 micdenny/rabbitmq-windows:3.9.22-servercore-ltsc2019 
Or
docker run -d --hostname my-rabbit --name some-rabbit2 micdenny/rabbitmq-windows:3.9.22-servercore-ltsc2022 

⁠Management Plugin

The management plugin⁠ is installed and enabled by default, which is available on the standard management port of 15672, with the default username and password of guest / guest.

You can then go to http://hostname:15672 in a browser and use user/password to gain access to the management console.