Remove debian bookworm images

[eshattow]

• Remove bookworm images EOL since 2026-07-11

[agners]

Hm, they are still under LTS 🤔 Did we remove Debian releases in the past after the official support period ended?

We even have a couple of apps in our main repositories which still use bookworm 🙈 .

[eshattow]

Sure, I'm following along with "We support versions that are not EOL" language of README.md

The previous Debian bullseye Release 2021-08-14, EOL 2024-08-14, LTS ending 2026-08-31; Removed in commit 064e019 authored 2025-08-06 #307 (merged same day) due to some failures building armhf target.

What users of bookworm remain?

[agners]

What users of bookworm remain?

In the https://github.com/home-assistant/addons/ repository:

$ grep -r -e debian */build.yaml
assist_microphone/build.yaml:  amd64: ghcr.io/home-assistant/amd64-base-debian:bookworm
assist_microphone/build.yaml:  aarch64: ghcr.io/home-assistant/aarch64-base-debian:bookworm
deconz/build.yaml:  aarch64: ghcr.io/home-assistant/aarch64-base-debian:bookworm
deconz/build.yaml:  amd64: ghcr.io/home-assistant/amd64-base-debian:bookworm
letsencrypt/build.yaml:  aarch64: ghcr.io/home-assistant/aarch64-base-debian:trixie-2025.12.2
letsencrypt/build.yaml:  amd64: ghcr.io/home-assistant/amd64-base-debian:trixie-2025.12.2
mosquitto/build.yaml:  aarch64: ghcr.io/home-assistant/aarch64-base-debian:trixie
mosquitto/build.yaml:  amd64: ghcr.io/home-assistant/amd64-base-debian:trixie
openthread_border_router/build.yaml:  aarch64: ghcr.io/home-assistant/aarch64-base-debian:trixie
openthread_border_router/build.yaml:  amd64: ghcr.io/home-assistant/amd64-base-debian:trixie
openwakeword/build.yaml:  amd64: ghcr.io/home-assistant/amd64-base-debian:bookworm
openwakeword/build.yaml:  aarch64: ghcr.io/home-assistant/aarch64-base-debian:bookworm
piper/build.yaml:  amd64: ghcr.io/home-assistant/amd64-base-debian:bookworm
piper/build.yaml:  aarch64: ghcr.io/home-assistant/aarch64-base-debian:bookworm
silabs-multiprotocol/build.yaml:  aarch64: ghcr.io/home-assistant/aarch64-base-debian:bullseye
silabs-multiprotocol/build.yaml:  amd64: ghcr.io/home-assistant/amd64-base-debian:bullseye
speech_to_phrase/build.yaml:  amd64: ghcr.io/home-assistant/amd64-base-debian:bookworm
speech_to_phrase/build.yaml:  aarch64: ghcr.io/home-assistant/aarch64-base-debian:bookworm
whisper/build.yaml:  amd64: ghcr.io/home-assistant/amd64-base-debian:bookworm
whisper/build.yaml:  aarch64: ghcr.io/home-assistant/aarch64-base-debian:bookworm

Mostly voice apps 🤔 . I'll ping the voice people, lets see that we can update them.

I guess since we now add the docker-base release to the tag, the bookworm tag anyways does not get updated, so removing them doesn't really make a difference in practice 🤷 .

[agners]

I guess since we now add the docker-base release to the tag, the bookworm tag anyways does not get updated, so removing them doesn't really make a difference in practice 🤷 .

I take that back, that is not true: We still update the bookworm tag on release. So leaving bookworm in this repository would make sure that we get the latest (LTS supported) Debian base...

[agners]

I'd rather prefer to keep the image for now still. Yes, we previously removed the bullseye images earlier, but the main reason there was that our armhf based on Debian armel wasn't covered by their LTS releases (see https://wiki.debian.org/LTS). The currently supported architecture are both supported by LTS, so I don't see a good reason to remove it right now.

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[sairon]

Sure, I'm following along with "We support versions that are not EOL" language of README.md

Note that this applies to Alpine images (the phrase you cited is followed by a link to the Alpine releases overview). Alpine and Debian have different support policies - there's no LTS for Alpine and there's bigger overlap of currently supported releases.

I agree with @agners that we should not remove these images yet. Instead, if the wording in the readme causes some confusion, say we keep images for supported base OS images, instead of using the term "EOL" which varies per distribution.

[eshattow]

Sure, I'm following along with "We support versions that are not EOL" language of README.md

Note that this applies to Alpine images (the phrase you cited is followed by a link to the Alpine releases overview). Alpine and Debian have different support policies - there's no LTS for Alpine and there's bigger overlap of currently supported releases.

I agree with @agners that we should not remove these images yet. Instead, if the wording in the readme causes some confusion, say we keep images for supported base OS images, instead of using the term "EOL" which varies per distribution.

In Debian parlance this would be oldoldstable, oldstable, stable, testing, and sid; Do you want supported Debian images by these names or by "End of Life (EOL)" "End of LTS" "End of ELTS" dates at https://www.debian.org/releases/

[sairon]

In Debian parlance this would be oldoldstable, oldstable, stable, testing, and sid; Do you want supported Debian images by these names or by "End of Life (EOL)" "End of LTS" "End of ELTS" dates at debian.org/releases

Let's simply claim support for stable releases and older releases that are still under LTS support. ELTS is a paid service. Also, seems that LTS support and [[old]old]stable terminology doesn't fully align with LTS support frames - Buster came out of LTS while still being oldoldstable before Trixie release.

[eshattow]

In Debian parlance this would be oldoldstable, oldstable, stable, testing, and sid; Do you want supported Debian images by these names or by "End of Life (EOL)" "End of LTS" "End of ELTS" dates at debian.org/releases

Let's simply claim support for stable releases and older releases that are still under LTS support. ELTS is a paid service. Also, seems that LTS support and [[old]old]stable terminology doesn't fully align with LTS support frames - Buster came out of LTS while still being oldoldstable before Trixie release.

Addition of support statements submitted as #389 and #390. Thanks!

[sairon]

@eshattow With the readme clarified, I think there's no reason to keep this opened, is there?

[eshattow]

@eshattow With the readme clarified, I think there's no reason to keep this opened, is there?

Fine with me to close this until Bookworm End of LTS date 2028-06-30; filed home-assistant/addons#4786.