readystack/rabbitmq repository overview

⁠RabbitMQ

readystack/rabbitmq:4.4.0-CE-ubuntu24.04-r2

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/rabbitmq/recipe⁠
• Upstream source at this release's pinned commit (v4.4.0): https://github.com/rabbitmq/rabbitmq-server/tree/24d5157cd415ef396c8ecd40a2d08c4d7ad3da9f⁠
• Product page: https://readystack.dev/products/rabbitmq⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/rabbitmq⁠
• Release history (JSON): https://readystack.dev/api/releases/rabbitmq⁠
• Defect record: https://readystack.dev/defects.html?product=rabbitmq⁠
• Today's scan: https://readystack.dev/products/rabbitmq#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=rabbitmq⁠
• Signing key (cosign): https://readystack.dev/keys/cosign.pub⁠

A cosign-signed build of github.com/rabbitmq/rabbitmq-server 4.4.0 (MPL-2.0), built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Developers and operations teams who connect applications, microservices and IoT devices through messaging.

Why: RabbitMQ is an open-source messaging and streaming broker. It supports several open protocols, including AMQP, MQTT and STOMP, and offers replicated queues and streams for data safety.

Use case: A web shop must not lose orders when its invoicing service is slow or down. The shop publishes each order to a RabbitMQ queue, the invoicing service works through the queue at its own pace, and a replicated queue keeps the orders safe if a broker node fails.

About the upstream project, written from its own description: https://github.com/rabbitmq/rabbitmq-server⁠ · https://www.rabbitmq.com/⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:d929996f173df55591ed485c5d4b91464cf318345cae52a1a590864d08b3cb5e on 2026-10-27.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v1, the rubric ce.rodeo published until 2026-10-26) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/rabbitmq⁠
• ReadyStack release check — passed at release on 2026-10-27: no fixable critical or high vulnerability (Docker Scout and OSV), a non-root user, SBOM and provenance attached. This is ReadyStack's own test, not a Docker grade; vulnerabilities published since then are in today's result at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key (fingerprint 04daa92344a52dbc) on this release's index digest sha256:d929996f173df55591ed485c5d4b91464cf318345cae52a1a590864d08b3cb5e; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/rabbitmq:4.4.0-CE-ubuntu24.04-r2.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (rabbitmq).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is 4.4.0-CE-ubuntu24.04-r2 — the release listed at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is signed, attested (SBOM + provenance), and is provided under the ReadyStack Agreement⁠.

• Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer re-graded, and fixes appear only in newer releases: move to the current release. For a superseded release's build kit, ask support.

• Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.

# ✓ current release
docker pull readystack/rabbitmq:4.4.0-CE-ubuntu24.04-r2

# ✗ unsupported (do not pull)
docker pull readystack/rabbitmq:internal-...

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/rabbitmq:4.4.0-CE-ubuntu24.04-r2 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Deployment

Single container running a single-node RabbitMQ broker: the rabbitmq-server launcher script (PID 1) starts one self-contained Erlang/OTP VM (the BEAM VM). RabbitMQ IS its own datastore: an embedded metadata store (Khepri; the khepri_db feature flag is enabled) plus the message/queue store, all on the local filesystem under /var/lib/rabbitmq. NO relational/SQL database, NO external store, NO sidecar. The rabbitmq_management (UI + REST API) and rabbitmq_prometheus (metrics) plugins are enabled at build time. The image IS the complete running instance.

docker run -d --name rabbitmq -p 5672:5672 -p 15672:15672 -p 15692:15692 -v rabbitmq-data:/var/lib/rabbitmq readystack/rabbitmq:4.4.0-CE-ubuntu24.04-r2

⁠The full ReadyStack Hermetic Build Kit

The complete --network=none build kit for this image — plus admin/DB/API handbooks, the build's validation records, and its build provenance records — is a free download for any registered account at readystack.dev/products/rabbitmq⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:d1bb0cfc83942898f836cc5d6bc5ad0e5ea678ec8a44259cced81d33c1b8c6fc on 2026-10-27.

— ReadyStack · readystack.dev