Use correct arch when publishing app#114
Merged
Merged
Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR updates the Dockerfile to support multi-architecture builds by dynamically selecting the correct .NET runtime identifier based on the target platform. Instead of hardcoding the x64 architecture, the build process now conditionally publishes for either amd64 (x64) or arm64 architectures.
- Replaces hardcoded
linux-musl-x64runtime identifier with conditional logic - Adds
ARG TARGETPLATFORMto capture the build platform during Docker build - Uses shell conditional to select appropriate runtime identifier (
linux-musl-x64orlinux-musl-arm64)
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Mathieu Gamache (PrincessMadMath)
approved these changes
Aug 18, 2025
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.
Jira issue link: FENG-905