Build architecture-agnostic docker images #390
+25
−35
Conversation
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
2 participants
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.
Previously, we copied a specific tarball into the docker image. This doesn't work well for multiarch builds because we need different tarballs depending on the target architecture.
With this change, we copy the appropriate tarball from a directory which may contain tarballs for multiple architectures.
This changes the CLI interface for
docker/Makefile: It no longer receives aCRYSTAL_TARGZpath but a path to a directory with the tarball(s).The refactoring also simplifies the Makefile a little bit (but more to come).
CI workflow: https://app.circleci.com/pipelines/github/crystal-lang/crystal/19768/workflows/7c7d6601-8106-44dc-83c8-ab7f49a574cd
Ref #389