Repository navigation
⚡️(docker) build the frontend assets once on the native platform - #873
Merged
Merged
Conversation
The arm64 frontend image ran yarn install and build under QEMU, taking about 20 minutes. The output is static files, so build them on the runner platform and only keep the nginx stage per architecture.
kernicPanel
force-pushed
the
ci/frontend-native-build
branch
from
October 16, 2026 12:53
4cd0a6e to
5331a06
Compare
|
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.



Purpose
The
build-and-push-frontendjob takes about 25 minutes. Most of it isyarn installandyarn buildrunning for arm64 under QEMU (~21 min).Proposal
The build output is static files served by nginx, identical on every
architecture. Run the node stages on the runner platform and keep only the
nginx stage per architecture.
FROM --platform=$BUILDPLATFORMon thefrontend-depsstageto 4 min 20, the published amd64 and arm64 images serve the same files
as before (only the Next.js build id differs)