Fix glibc compat: switch to Debian Bullseye base image, bump Copilot CLI to v0.5.1

[Copilot]

The bookworm-based image ships a glibc version that causes Error relocating /usr/local/bin/copilot: fcntl64: symbol not found at runtime. Switching to bullseye resolves the symbol mismatch.

Changes

• Base image (Dockerfile): amd64-base-debian:bookworm → amd64-base-debian:bullseye (Debian 11)
• Base image (build.yaml): Updated both amd64 and aarch64 entries from bookworm to bullseye, ensuring the Home Assistant add-on build pipeline injects the correct base image
• Copilot CLI: COPILOT_VERSION v0.0.418 → v0.5.1

- ARG BUILD_FROM=ghcr.io/home-assistant/amd64-base-debian:bookworm
+ ARG BUILD_FROM=ghcr.io/home-assistant/amd64-base-debian:bullseye

- ARG COPILOT_VERSION=v0.0.418
+ ARG COPILOT_VERSION=v0.5.1

# addon/build.yaml
 build_from:
-  aarch64: ghcr.io/home-assistant/aarch64-base-debian:bookworm
-  amd64: ghcr.io/home-assistant/amd64-base-debian:bookworm
+  aarch64: ghcr.io/home-assistant/aarch64-base-debian:bullseye
+  amd64: ghcr.io/home-assistant/amd64-base-debian:bullseye

Original prompt

The current Dockerfile uses the ghcr.io/home-assistant/amd64-base-debian:bookworm base image, which is causing a glibc compatibility issue leading to the error Error relocating /usr/local/bin/copilot: fcntl64: symbol not found.

To resolve this, the Dockerfile should be updated to use the ghcr.io/home-assistant/amd64-base-debian:bullseye image, which is based on Debian 11 ("Bullseye"). This will provide an older, more compatible version of glibc.

Additionally, the COPILOT_VERSION argument should be updated to v0.5.1 to use a more recent version of the Copilot CLI.

This pull request was created from Copilot chat.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull request overview

Updates the Home Assistant add-on container build to address a glibc compatibility issue affecting the bundled GitHub Copilot CLI runtime.

Changes:

• Switch the add-on Docker base image default from Debian Bookworm to Debian Bullseye.
• Bump the pinned GitHub Copilot CLI release from v0.0.418 to v0.5.1.

[Copilot]

Changing the default BUILD_FROM here likely won’t affect how the add-on is actually built/published, because Home Assistant’s add-on build pipeline typically injects BUILD_FROM from addon/build.yaml (which still points to the bookworm images). As a result, the PR’s stated glibc fix may not take effect unless build.yaml is also updated to bullseye (for both amd64 and aarch64, as applicable).

[tserra30]

@copilot apply changes based on the comments in this thread

[Copilot]

@copilot apply changes based on the comments in this thread

Updated addon/build.yaml (commit 9228ffc) to switch both amd64 and aarch64 entries from bookworm to bullseye, so the build pipeline will now inject the correct base image:

build_from:
  aarch64: ghcr.io/home-assistant/aarch64-base-debian:bullseye
  amd64: ghcr.io/home-assistant/amd64-base-debian:bullseye