Skip to content

feat(docker): Add multi-platform support for Docker build#541

Open
gondoi wants to merge 1 commit intomainfrom
feature/devops-1248-enable-multi-arch-build-containers-group-1
Open

feat(docker): Add multi-platform support for Docker build#541
gondoi wants to merge 1 commit intomainfrom
feature/devops-1248-enable-multi-arch-build-containers-group-1

Conversation

@gondoi
Copy link
Copy Markdown

@gondoi gondoi commented Apr 20, 2026

No description provided.

@cursor
Copy link
Copy Markdown

cursor Bot commented Apr 20, 2026

PR Summary

Low Risk
Low risk GitHub Actions change that only affects Docker build outputs; main risk is longer builds or platform-specific build failures when producing arm64 images.

Overview
Updates the composite GitHub Action ./.github/actions/docker-publish to publish multi-platform Docker images by building for linux/amd64 and linux/arm64 in the docker/build-push-action step.

Reviewed by Cursor Bugbot for commit 09dfbca. Bugbot is set up for automated code reviews on this repo. Configure here.

Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 2 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 09dfbca. Configure here.

id: publish
with:
context: ${{ inputs.context }}
platforms: linux/amd64,linux/arm64
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Multi-platform builds produce empty imageid output

Low Severity

Adding platforms: linux/amd64,linux/arm64 causes docker/build-push-action to produce an empty imageid output, since multi-platform builds create a manifest list rather than a single image. The composite action still declares imageid as an output and displays it in the build summary, both of which will now always be empty strings. Any downstream consumer relying on this output will silently receive no value.

Additional Locations (2)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 09dfbca. Configure here.

id: publish
with:
context: ${{ inputs.context }}
platforms: linux/amd64,linux/arm64
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing QEMU setup breaks arm64 platform build

High Severity

Adding platforms: linux/amd64,linux/arm64 requires QEMU emulation for arm64 on x86_64 GitHub Actions runners, but docker/setup-qemu-action is not present before docker/setup-buildx-action. The Dockerfile's final stage (FROM debian:bookworm-slim) runs apt-get under the target platform, which will fail for arm64 without QEMU's binfmt_misc handlers registered. The build stages avoid this by using --platform=$BUILDPLATFORM, but the runtime stage does not.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 09dfbca. Configure here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant