Page MenuHomePhabricator

Create TCL image for Toolforge based on a supported Debian release
Closed, ResolvedPublic

Description

Per https://k8s-status.toolforge.org/images/docker-registry.tools.wmflabs.org/toolforge-tcl86-sssd-web:latest/ there are two tools (giftbot & linksearch) actively using the TCL image that is using a deprecated Debian stretch base image. Debian has dropped stretch from their mirror servers making rebuilding this image problematic at best.

We should make a replacement TCL image based on a supported Debian release and let the https://toolsadmin.wikimedia.org/tools/id/giftbot and https://toolsadmin.wikimedia.org/tools/id/linksearch maintainers know about it.

Event Timeline

Buster has TCL 8.6.9 and bullseye has TCL 8.6.11. The legacy stretch container has TCL 8.6.6. I think we can just reuse the existing tcl86/tcl8.6 labels and bump the base image to bullseye without anything scary happening.

@Giftpflanze and @doctaxon does that sound reasonable to the two of you?

Why 8.6? There's already tcl/tk 8.7 out.

Why 8.6? There's already tcl/tk 8.7 out.

We generally install system packages produced by the Debian project. Today the most recent version of Debian that we are supporting in Toolforge is Debian Bullseye. Per https://packages.debian.org/bullseye/tcl, 8.6.11 is the version that would be available. Debian Bookworm is the "testing" release that will become stable next and it will have 8.6.13.

Change 912343 had a related patch set uploaded (by BryanDavis; author: Bryan Davis):

[operations/docker-images/toollabs-images@master] tcl86: switch base image to bullseye

https://gerrit.wikimedia.org/r/912343

okay, feel free to update tcl/tk

Change 912343 merged by jenkins-bot:

[operations/docker-images/toollabs-images@master] tcl86: switch base image to bullseye

https://gerrit.wikimedia.org/r/912343

bd808 claimed this task.
$ webservice tcl8.6 shell
shell-1682634486:~$ echo 'puts [info patchlevel];exit 0' | tclsh
8.6.11

The next time that the giftbot and linksearch services are restarted they should pick up the new container from the registry.