fix(docker): Use proper Erlang binaries for our builds #577
Conversation
This file contains 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
The existing package paths for the compiled Erlang binaries are no longer valid. This patch fixes them with the new ones and fixes Docker image building. Note that we are using the binaries compiled for Debian `bullseye` instead of our `bookworm` version as they are not available yet. One needs to check https://www.erlang-solutions.com/downloads/#
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.
The existing package paths for the compiled Erlang binaries
are no longer valid. This patch fixes them with the new ones
and fixes Docker image building.
Note that we are using the binaries compiled for Debian
bullseyeinstead of our
bookwormversion as they are not available yet.One needs to check https://www.erlang-solutions.com/downloads/#