Kevin,
On 3/25/21 7:40 PM, Fox, Kevin M wrote:
> That would be unfortunate. Some clusters won't be able to distinguish if
> there is an update or not.
If your toolchain is unable to correctly handle changing tags for Docker
Images then it is completely broken. This is happening all the time
. -3 next, etc. Could something like that
be adopted?
Thanks,
Kevin
From: Tim Düsterhus
Sent: Thursday, March 25, 2021 11:32 AM
To: Paul Lockaby
Cc: Lukas Tribus; haproxy
Subject: Re: OpenSSL Security Advisory
Check twice before you click! This email
Paul,
On 3/25/21 7:31 PM, Paul Lockaby wrote:
> Thanks for all of the responses! So the image version number for HAProxy
> stays the same but the hash will update?
>
Yes exactly.
Best regards
Tim Düsterhus
Thanks for all of the responses! So the image version number for HAProxy stays
the same but the hash will update?
> On Mar 25, 2021, at 9:03 AM, Tim Düsterhus wrote:
>
> Paul,
>
> On 3/25/21 4:46 PM, Paul Lockaby wrote:
>> As a lurker on this list I've always kind of wondered what the policy
[…]
> On 25.03.2021., at 17:03, Tim Düsterhus 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
Paul,
On 3/25/21 4:46 PM, Paul Lockaby wrote:
> As a lurker on this list I've always kind of wondered what the policy
is for releasing new containers to address security patches on
dependencies like this. I'm not sure who maintains the "official"
containers for HAProxy but would they do a
Hello!
As a lurker on this list I've always kind of wondered what the policy is for
releasing new containers to address security patches on dependencies like this.
I'm not sure who maintains the "official" containers for HAProxy but would they
do a re-release of the latest versions to include
7 matches
Mail list logo
