Re: [PATCH 2/2] contrib: hashserv: Dockerfile: Update base image
Frieder Schrempf <[email protected]>
| Newsgroups | org.openembedded.lists.bitbake-devel |
|---|---|
| Message-ID | <[email protected]> |
On 14.05.26 12:18, Paul Barker wrote: > On Mon, 2026-05-11 at 17:36 +0200, Frieder Schrempf wrote: >> From: Frieder Schrempf <[email protected]> >> >> Alpine 3.13 is out-of-date and doesn't provide a Python version that >> is comaptible with the current version of bitbake master. Fix this >> by upgrading the alpine base image and installing the missing >> websockets module. >> >> Signed-off-by: Frieder Schrempf <[email protected]> >> --- >> contrib/hashserv/Dockerfile | 4 ++-- >> 1 file changed, 2 insertions(+), 2 deletions(-) >> >> diff --git a/contrib/hashserv/Dockerfile b/contrib/hashserv/Dockerfile >> index fe7e091ec..5c8b8dd11 100644 >> --- a/contrib/hashserv/Dockerfile >> +++ b/contrib/hashserv/Dockerfile >> @@ -9,9 +9,9 @@ >> # docker build -f contrib/hashserv/Dockerfile . >> # >> >> -FROM alpine:3.13.1 >> +FROM alpine:3.23 >> >> -RUN apk add --no-cache python3 libgcc >> +RUN apk add --no-cache python3 py3-websockets libgcc >> >> COPY bin/bitbake-hashserv /opt/bbhashserv/bin/ >> COPY lib/hashserv /opt/bbhashserv/lib/hashserv/ > > Thanks for sending this! Alpine 3.13 was end-of-life 3.5 years > ago [1]... > > We also need to update the Dockerfile for prserv. I wonder if we should > just use alpine:latest in both of them. > > [1]: https://endoflife.date/alpine-linux Yes, alpine:latest would also work for me. The downside would be that image builds could break silently if compatibility issues between bitbake and the latest alpine release occur. The more stable solution would be to pin the alpine version and have CI builds and tests for the image. Anyway, for me this was just a drive-by fix while I was building a hashserv image from the official Dockerfile and I don't have any strong opinions here.