Restore arm64 docker image support#212
Merged
dennisvang merged 4 commits intodevelopfrom Jul 15, 2025
Merged
Conversation
Contributor
Author
|
We can work around the Now install succeeds, but we run into another issue in the build phase: Actually this error also occurs if we run |
8784f3a to
a74e66e
Compare
according to [1], both packages expose the same JS API [1]: https://sass-lang.com/blog/libsass-is-deprecated/#how-do-i-migrate
instead we rely on the default, which is "linux/amd64,linux/arm64"
MarekSuchanek
approved these changes
Jul 15, 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.
This fixes the build issue that prevented us from creating an arm64 image:
node-sassdependency by latestsass(according to sass docs, both packages expose the same JS API)
sassupgradefixes #188