Repository navigation
tag debian bookworm based images with tag x-bookworm #34
Description
Currently when I want to use the debian bookworm based image, I need to pull e.g. the tag "5" for the latest version 5 image. The tag is not named "5-bookworm" in the same way the debian bullseye images are.
Without having the image tag x-bookworm, it may occur that with future debian versions the image changes from bookworm to trixie or whatever comes next. This could cause problems with collations and the underlying libicu version.
Therefore it would be nice to be able to pull the tag 5-bookworm to be sure that libicu does not change unintentionally.
Thank you in advance.
Activity
Phase 3: Tagging System
Phase 3: Tagging System
fdcastel commentedon Apr 7, 2026
@level420 I’m putting together a new set of images available here.
They feature an updated tagging scheme, along with the Firebird 6 snapshot version.
If you have a chance, could you test it and share your feedback on #36?
level420 commentedon Apr 20, 2026
@fdcastel sorry for being late with my answer.
I've tried to pull, but I'm getting this error:
level420 commentedon Apr 20, 2026
OMG! Coffee hasn't kicked in yet! But it doesn't work:
fdcastel commentedon Apr 20, 2026
@level420 Sorry about that — two issues with the pull command:
firebird/segment and tag separator. Correct form isdocker pull ghcr.io/fdcastel/firebird:<tag>(e.g.ghcr.io/fdcastel/firebird:3-bullseye).3-bullseyetag yet — the initial publish only covered Firebird 5 / bookworm. I'm now building all missing variants across Firebird 3, 4, 5 × bookworm/bullseye/jammy/noble. This will take a while (~30–60 min of CI time), but3-bullseyeis first in the queue. I'll follow up once it's pushed. Thanks for checking this out!fdcastel commentedon Apr 20, 2026
@level420 Images are now built and available. Two notes on your earlier command:
The original
docker pull ghcr.io/fdcastel/3-bullseyewas missing the image name and tag separator — Docker read3-bullseyeas the repo name rather than a tag, which is why it tried to pulllatestand got denied. The correct form is:Also, when you tried, the
3-bullseyetag didn't actually exist yet — the initial publish only covered Firebird 5 / bookworm. That's now fixed: the full matrix is published, including all 3.x, 4.x, and 5.x variants across bookworm/bullseye/jammy/noble, plus6-snapshotand5-snapshot. v5 tags are multi-arch (amd64 + arm64); v3 and v4 are amd64-only (no upstream arm64 releases).Some examples:
Thanks for testing — your report surfaced a latent PowerShell 7 bug in the multi-arch publish path as well, now fixed. Feedback on the images and the new tagging scheme is very welcome.
level420 commentedon Apr 22, 2026
@fdcastel I've tested 3-bullseye, 4-bullseye and 5-bullseye, as I'm using them here with my webapps. It was a simple replace without any problems so far. Did not find the time to test 6-snapshot yet. With 6-snapshot: it would be helpful to know what the base was (bullseye, bookworm etc.).
Currently I'm moving all of my image armada from debian bullseye and bookworm to trixie. It would be great to have the trixie images as well.
fdcastel commentedon Apr 22, 2026
@level420 thanks for pointing out about
trixie: I’d completely overlooked it. 🤦🏻♂️And thanks for the tip about the snapshots base image as well. 👍🏻
I’m updating all the images now, though it’ll take a while (probably 1–2 hours).
Phase 3: Tagging System