readystack/haproxy repository overview

⁠HAProxy

readystack/haproxy:3.4.6-CE-ubuntu24.04-r7

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/haproxy/recipe⁠
• Upstream source at this release's pinned commit (v3.4.6): https://git.haproxy.org/?p=haproxy-3.4.git;a=commit;h=56332c50b5291cfbbfd440d958adc988fbf87e2f⁠
• Product page: https://readystack.dev/products/haproxy⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/haproxy⁠
• Release history (JSON): https://readystack.dev/api/releases/haproxy⁠
• Defect record: https://readystack.dev/defects.html?product=haproxy⁠
• Today's scan: https://readystack.dev/products/haproxy#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=haproxy⁠
• Signing key (cosign): https://readystack.dev/keys/cosign.pub⁠

A cosign-signed build of HAProxy 3.4.6 from https://git.haproxy.org/git/haproxy-3.4.git⁠, tag v3.4.6 (2026-09-28), built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Operations teams and site reliability engineers who run busy websites and services that need load balancing and high availability.

Why: HAProxy is a reverse proxy and load balancer for TCP and HTTP applications. It spreads traffic across servers, checks their health, terminates TLS, and can rate-limit or block abusive clients.

Use case: An online shop runs its web application on several servers. HAProxy in front terminates HTTPS, sends each request to a server that passes its health checks, keeps a shopper's session on the same server, and slows down or blocks clients that send abusive request rates.

About the upstream project, written from its own description: https://www.haproxy.org/⁠ · https://github.com/haproxy/haproxy/blob/master/doc/intro.txt⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:bb7c69b0b5d7ae35f2f9f35e86872c750c309d0ef5a1b6e73872bbca69be0d75 on 2026-11-12.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v2, ce.rodeo's current rubric; scans before 2026-11-08 used cerodeo-v1) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/haproxy⁠
• ReadyStack release check — passed at release on 2026-11-12: 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:bb7c69b0b5d7ae35f2f9f35e86872c750c309d0ef5a1b6e73872bbca69be0d75; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/haproxy:3.4.6-CE-ubuntu24.04-r7.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (haproxy).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is 3.4.6-CE-ubuntu24.04-r7 — 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.

• Release tags never move, so pulling the same tag again never changes the image. To be offered each new release automatically (a new revision r<N+1>, or a new upstream version), use the ReadyStack Renovate preset: https://readystack.dev/updates.html⁠

• 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/haproxy:3.4.6-CE-ubuntu24.04-r7

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

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

⁠Deployment

Single container. HAProxy runs in master-worker mode in the foreground (haproxy -W -db; doc/management.txt: -W starts a master that monitors the workers, -db disables background mode): the master is the container's main process and starts the worker that handles traffic. Compiled from source by this image's build (make TARGET=linux-glibc ...). No database, no sidecar, nothing stored on disk. The shipped configuration is a placeholder that proxies nothing: it answers on port 8080 with a placeholder message and serves statistics and metrics only on 127.0.0.1:8404 inside the container. To load-balance your services, mount a directory holding your haproxy.cfg over /usr/local/etc/haproxy (for example -v "$PWD/haproxy":/usr/local/etc/haproxy:ro; see Config reload in the handbooks).

docker run -d --name haproxy -p 8080:8080 readystack/haproxy:3.4.6-CE-ubuntu24.04-r7

With the shipped configuration, http://localhost:8080/healthz⁠ answers 'Service ready.' and every other path answers a plain-text message saying the placeholder configuration is in use. To proxy your services, put your configuration in a directory as haproxy/haproxy.cfg and mount that directory over /usr/local/etc/haproxy (read-only is fine), for example -v "$PWD/haproxy":/usr/local/etc/haproxy:ro, so that later edits reach the container (see Config reload in the handbooks), and publish the ports your frontends bind. HAProxy runs as the non-root haproxy user, so the file must be readable by that user (see Ports in the handbooks for binding ports below 1024).

⁠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/haproxy⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:d5bf35c5dfe7dc8b26d5f3d0d329eb2580fa5d3a10cac8b0e5a186bb74623f3a on 2026-11-12.

— ReadyStack · readystack.dev