Draft
fix: restore -tags WKAFKA in Dockerfile build command#506
Conversation
The build failed because: 1. (v1.1.x branch) Used golang:1.18-buster / debian:buster which reached end-of-life — repositories return 404 causing apt-get to fail. 2. (v1.1.x branch) Referenced non-existent root-level main.go instead of cmd/birdwatcher/main.go. 3. Both branches: -tags WKAFKA was missing from the go build command, which disabled the Kafka message-queue factory at runtime. Changes in this commit (targeting the main branch Dockerfile): - Add -tags WKAFKA to enable the Confluent Kafka factory - Remove accidental blank line The v1.1.x branch Dockerfile has all of the above issues and should be updated to match this fixed version (golang:1.24-bookworm base image, proper apt-get-install, module-cache layer, -tags WKAFKA, bookworm-slim runtime image).
Collaborator
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Copilot The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Copilot
AI
changed the title
[WIP] Fix failing GitHub Actions job build-and-push
fix: restore -tags WKAFKA in Dockerfile build command
Jul 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
build-and-pushCI job failed on thev1.1.xbranch because the Dockerfile used EOL Debian Buster images (golang:1.18-buster,debian:buster) whose package repositories now return 404, causingapt install gccto exit with code 100. Thev1.1.xDockerfile also referenced a non-existent root-levelmain.goinstead ofcmd/birdwatcher/main.go.Changes
-tags WKAFKAin thego buildcommand, which was accidentally dropped when the base images were updated to Bookworm in chore: update dockerfile #420; without this tag themq/factory_wkafka.goConfluent Kafka factory is excluded from the binary at compile timeNote
The
v1.1.xbranch Dockerfile still carries all the original issues (Buster base images, bareapt install, wrongmain.gopath). It needs a separate backport of the full fix shown here.