Bookworm is planned to release in about a month and a half, so it would be nice to have a Docker base image to start testing on.
Previous work: T281596: Publish wikimedia-bullseye base docker image
Description
Description
Details
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Stalled | None | T335352 Provide a PHP 8.2 image for Kubernetes toolforge-jobs and webservice | |||
| Stalled | None | T335507 Build Bookworm based Toolforge Kubernetes images | |||
| Stalled | Joe | T335560 Publish Wikimedia bookworm base Docker image |
Event Timeline
Comment Actions
Mentioned in SAL (#wikimedia-operations) [2023-05-15T05:36:23Z] <_joe_> building bookworm image for the first time T335560
Comment Actions
Change 919611 had a related patch set uploaded (by Giuseppe Lavagetto; author: Giuseppe Lavagetto):
[operations/puppet@production] docker::baseimages: support bookworm
Comment Actions
Change 919611 merged by Giuseppe Lavagetto:
[operations/puppet@production] docker::baseimages: support bookworm
Comment Actions
While I've added bookworm to the build process, I think I'll revert that part of my change.
Every time I try to run a build there is a different symlink broken on snapshots.debian.org making the process fail.
I guess we're better off waiting for the official release.
The last issue I encountered happened *after* the base system was installed (so, success compared to other runs!):
warning: no apparent 'bookworm/main' for 'amd64' on any of the following; skipping - http://snapshot.debian.org/archive/debian/20230516T063700Z warning: no apparent 'bookworm/updates/main' for 'amd64' on any of the following; skipping - http://snapshot.debian.org/archive/debian-security/20230516T063700Z warning: no apparent 'bookworm-updates/main' for 'amd64' on any of the following; skipping - http://snapshot.debian.org/archive/debian/20230516T063700Z error: sources.list ended up empty -- something is definitely wrong
which makes it look like some logic has changed in how the debian archives are organized for bookworm. I'll need to dig deeper.
Comment Actions
It's much simpler than that - debuerreotype would work correctly - the problem is that snapshots are full of broken links for bookworm - again:
http://snapshot.debian.org/archive/debian/20230515T030231Z/dists/bookworm/main/binary-amd64/ lists Packages.gz as a symlink to a hash url that doesn't exist.
I'll revert the build step for bookworm and set this task to stalled for the moment - it's simply too un predictable if a bookworm image will be built or not.
Comment Actions
Change 920196 had a related patch set uploaded (by Giuseppe Lavagetto; author: Giuseppe Lavagetto):
[operations/puppet@production] docker::baseimages: skip building bookworm
Comment Actions
Change 920196 merged by Giuseppe Lavagetto:
[operations/puppet@production] docker::baseimages: skip building bookworm
Comment Actions
After discussion with @MoritzMuehlenhoff - it makes sense that snapshots might be broken right now that things change hectically for a testing distro before the freeze - we should pick up this task after June 3rd when the freeze will be enacted.