Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare static binaries for release targets and docker runtimes, and dynamic binaries for local development #3856

Merged
merged 2 commits into from
Dec 14, 2022

Conversation

jkneubuh
Copy link
Contributor

Type of change

  • Bug fix

Description

This PR fixes two problems with the release-2.5 Makefile:

  • On rancher desktop, TARGETOS AND TARGETARCH are not automatically set by the "docker" build agent, leading to an error when building the image locally without buildx or builders from docker.io. This sets the variables to linux and go env GOARCH when building the containers locally, aligning with the default values set by buildx.

  • The introduction of statically linked binaries was necessary for running ARM64 on the Alpine containers, but it caused a regression and forced the peer to sigsegv when built locally on an emulated ubuntu64 linux. With this update, the locally built peer images will continue to be created as dynamically linked binaries, with the static linking enabled only for the release target and for binaries deployed to alpine in Docker.

Related issues

Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
@jkneubuh jkneubuh requested a review from a team as a code owner December 14, 2022 20:02
@jkneubuh jkneubuh changed the title Rel 2.5/bugfix/lcrt0 Prepare static binaries for release targets and docker runtimes, and dynamic binaries for local development Dec 14, 2022
@denyeart denyeart merged commit c66ea41 into hyperledger:release-2.5 Dec 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants