Delta.bg MarketplaceMarketplace
RabbitMQ (AlmaLinux 8)

RabbitMQ (AlmaLinux 8)

  • OS: almalinux 8

Description

This image combines RabbitMQ with AlmaLinux 8 so you can start with a ready-to-run environment instead of manual provisioning. It is optimized for asynchronous messaging and queue-based workflows, while keeping the underlying operating system stable and maintainable for long-term operations. Choose this stack when you want to reduce setup time, standardize infrastructure, and launch RabbitMQ-based workloads on AlmaLinux 8 quickly.

  1. Software included
  2. Initial start of the service
  3. Quick settings and frequently asked questions
  4. Working with Docker
    1. Restarting all services
    2. Recreating Docker containers
    3. Checking the status of the Docker application

Software included

Package Version
RabbitMQ latest
Docker 3.20.10
Docker compose 2.12.2
containerd.io 1.6.10

Initial start of the service

This application uses Docker to provide faster startup of the underlying software (RabbitMQ) and direct use of it. This eliminates the need to familiarize yourself with its specifics in terms of configuration and installation. To start working directly with the application, all you need to do is connect your application that will use RabbitMQ by giving it the IP address assigned to your virtual machine and the port RabbitMQ is listening on (described below).

Quick settings and frequently asked questions

  • Logging into the cloud service is done using an SSH key or password that you have specified.
  • Docker is installed as recommended by the official docker documentation.
  • The standard docker and docker compose commands are now available in this application.
  • When the virtual machine is first started, it takes a few minutes before a Docker container containing RabbitMQ is started.
  • RabbitMQ data is set to be persistent and is located in /opt/rabbitmq/data/.
  • By default, RabbitMQ runs on all available interfaces on the machine. RabbitMQ access ports are 4369, 5551, 5552, 5672, 25672 and 15672.

Working with Docker

The organization of this application is entirely done using Docker. In this way, we can provide you with ready-made applications faster. In addition, their configuration is more flexible and quite controllable. To be able to control this application, however, you need to know some basic Docker functionalities and features.

Restarting all services

Restarting the database and the Docker container that contains RabbitMQ itself, along with the rest of the software, can be done in two ways:

  1. By restarting the entire virtual machine
  2. Restarting the Docker containers, which is the faster option. To do this, access your machine via SSH, and run the following commands:
sudo su -
cd /opt/docker-rabbitmq/
docker compose restart

Recreating Docker containers

Recreation of a Docker container may be necessary if you've changed the configuration inside the docker-compose.yml file. If there are changes, please follow these steps:

cd /opt/docker-rabbitmq/
docker compose stop
docker compose up -d

Checking the status of the Docker application

To check, you need to run the following commands:

sudo su -
docker ps -a

Please pay attention to the STATUS column. It should show how long the service has been running, for example Up X minutes. If the status is Restarting then you need to check what is wrong with the application. In such a case, you can check by following the application logs as follows:

  1. Get the application name that you can see in the NAMES column from the output of the docker ps -a command. View the logs with the docker logs <NAME> command, where is the name of the container.