Upgrade eventd docker container from bookworm to trixie

[yxieca]

Note: This PR was created with the assistance of an AI agent (OpenClaw/Claude).

Why I did it

Upgrade the eventd Docker container from Debian Bookworm to Debian Trixie as part of the ongoing SONiC Trixie migration effort tracked in sonic-net/SONiC#2169.

How I did it

• Changed the base image for docker-eventd from docker-config-engine-bookworm to docker-config-engine-trixie
• Updated the Dockerfile template and associated build rules to target the Trixie base

How to verify it

1. Build a sonic-vs image: make PLATFORM=vs target/sonic-vs.img.gz
2. Deploy the image and verify the eventd container is running
3. Exec into the container and confirm it is based on Debian Trixie:

   docker exec -it eventd cat /etc/os-release
   # Should show Debian GNU/Linux trixie/sid or version 13
   

Which release branch to backport

None — this is a master-only change for the Trixie migration.

Tested branch

• Built and deployed sonic-vs image successfully
• Confirmed eventd container running on Debian Trixie (13.4)
• All eventd functionality verified working

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[Copilot]

Pull request overview

This PR upgrades the docker-eventd container to Debian Trixie as part of SONiC’s ongoing Trixie migration, by switching its base image and build-rule dependencies from the Bookworm config-engine image to the Trixie config-engine image.

Changes:

• Update docker-eventd build rules to depend on and load docker-config-engine-trixie (including debug deps/packages).
• Switch docker-eventd Dockerfile base image from docker-config-engine-bookworm to docker-config-engine-trixie.
• Move docker-eventd registration from the Bookworm docker list to the Trixie docker list.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
rules/docker-eventd.mk	Migrates docker-eventd build dependencies/load base to the Trixie config-engine image and registers it as a Trixie docker.
dockers/docker-eventd/Dockerfile.j2	Switches the container base image to docker-config-engine-trixie.

[Copilot]

By moving docker-eventd to SONIC_TRIXIE_DOCKERS (and removing it from the bookworm docker list), a bookworm build that enables INCLUDE_SYSTEM_EVENTD (via SONIC_INCLUDE_SYSTEM_EVENTD=y) will still add docker-eventd into SONIC_INSTALL_DOCKER_IMAGES, causing installers to depend on target/docker-eventd.gz. Since DOCKER_IMAGES for BLDENV=bookworm comes from SONIC_BOOKWORM_DOCKERS, there will be no rule to build target/docker-eventd.gz and the build will fail. Consider gating docker-eventd’s inclusion in SONIC_INSTALL_DOCKER_IMAGES to trixie builds only, or providing a separate bookworm variant if bookworm+system-eventd is still supported.