Hi Dinko.
Cool work, thanks :-)
Any plans to switch to "pebble" for HAProxy images similar to hug?
https://hub.docker.com/r/haproxytech/haproxy-unified-gateway
Regards
Aleks
On 2025-12-03 (Mi.) 10:16, Dinko Korunic wrote:
Hi everyone,
We have been overhauling HAProxy (haproxytech) CE Docker images lately, and here
is what we have now given that many of our users have been asking about this:
- regular Alpine/Debian/Ubuntu images with HAProxy 2.4 to 3.4 with Data Plane
API binary embedded (DP2.9 for HAProxy 2.x and DP3.x for HAProxy 3.x) for arm/
v6, arm/v7, arm64 and amd64 architectures --> these images have regular Docker
tags/labels corresponding to HAProxy CE releases and their branches (for
instance tags 3.3.0, 3.3 and latest all pointing to latest stable 3.3.0 version)
- same images in all variants as above, buth with S6-overlay installed so that
HAProxy and Data Plane API start by default (multiprocess Docker images with
minimal init system) for arm/v6, arm/v7, arm64 and amd64 architectures —> these
images have similar Docker tags/labels as above, but with s6 prefix (for
instance s6-3.3.0, s6-3.3).
All the above images (non-S6 and S6-enabled) are now based on latest AWS-LC
v1.65.1 and are all slimmed-down a bit more than before (by having AWS-LC
builder stage and HAProxy CE builder stage separately executed, so that only the
binary artefacts are transferred to a final image — we used to build and cleanup
HAProxy CE tree in the same layer).
Kind regards,
D.
--
Dinko Korunic ** Standard disclaimer applies **
Sent from OSF1 osf1v4b V4.0 564 alpha
