Re: [bitbake-devel] [PATCH] prserv/Dockerfile: Update to Alpine 3.23

Paul Barker <[email protected]> Mon, 18 May 2026 11:31:41 +0100

Newsgroups	org.openembedded.lists.bitbake-devel
Message-ID	<[email protected]>

On Mon, 2026-05-18 at 12:28 +0200, Quentin Schulz wrote:
> Hi Paul,
> 
> On 5/18/26 11:15 AM, Paul Barker via lists.openembedded.org wrote:
> > Alpine 3.13 is long obsolete, update to use the current version of
> > Alpine as our base image
> > 
> > Signed-off-by: Paul Barker <[email protected]>
> > ---
> >   contrib/prserv/Dockerfile | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/contrib/prserv/Dockerfile b/contrib/prserv/Dockerfile
> > index 9585fe3f076c..c630ce99722f 100644
> > --- a/contrib/prserv/Dockerfile
> > +++ b/contrib/prserv/Dockerfile
> > @@ -28,7 +28,7 @@
> >   # prserv
> >   #
> >   
> > -FROM alpine:3.14.4
> > +FROM alpine:3.23
> >   
> 
> FYI, these are "tags" but they have the same meaning as in git. They 
> aren't immutable and they actually are very often changed to point to a 
> different layer.
> 
> e.g. 3.23 currently points at the same layer as 3.23.4, but a month ago 
> it very likely was pointing at 3.23.3.
> 
> The only way to work around this limitation (if desired) is to use the 
> digest value of the tag as argument, this guarantees that alpine:3.23 is 
> the same from any machine and does not depend on when it was first 
> pulled or whether --pull=always was passed.
> 
> I'm not sure this is a necessity here but wanted to bring this up :)

Hi Quentin,

We do want to pick up the latest updates in the Alpine 3.23 series when
this container image is built. What we don't want is to automatically
jump to 3.24 or later without some human review as that may need some
other changes to be made in the Dockerfile.

Best regards,

-- 
Paul Barker

signature.asc (application/pgp-signature, 252 B)