[…]

> On 25.03.2021., at 17:03, Tim Düsterhus <t...@bastelstu.be> wrote:
> 

[…]

> 
> The 'haproxy' image for Docker is maintained by the Docker Official
> Images Team [1] [2]. They also handle the necessary rebuilds when the
> base image changes. I maintain 2 images as part of the Official Images
> program and also contribute to the HAProxy image via Pull Requests. I am
> not part of the DOI Team, though.
> 
> Independently from your email I already asked in their IRC whether the
> 'debian' base image is going to be rebuilt due to the OpenSSL update.
> This would then cause a rebuild of the 'haproxy' image.
> 
> For the images that contain a username (e.g. timwolla/haproxy) the
> authors are responsible to trigger a rebuild.
> 

Just to follow-up on this: As Tim has already kindly summarised, the same thing
also applies for haproxytech (https://hub.docker.com/u/haproxytech) HAProxy CE
images as well, they will get rebuilt on official base image (Debian, Ubuntu,
Alpine, etc.) being rebuilt.

This includes regular HAProxy CE images, Ingress Controller images, etc.


Kind regards,
D.

-- 
Dinko Korunic                   ** Standard disclaimer applies **
Sent from OSF1 osf1v4b V4.0 564 alpha


Reply via email to