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.

Sign up for GitHub

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

Jump to bottom

Re-enable docker build with static linking on alpine #26

Closed
KonradStaniec opened this issue Aug 19, 2024 · 0 comments · Fixed by #213
Closed

Re-enable docker build with static linking on alpine #26

KonradStaniec opened this issue Aug 19, 2024 · 0 comments · Fixed by #213
Assignees
@SebastianElvis
Labels
phase-2-readiness

Comments

@KonradStaniec
Copy link
Collaborator

Context:

This means:

  • we can update wasmd to version [v0.52.0](https://github.com/CosmWasm/wasmd/tree/v0.52.0)
  • we can go back docker images build on alpine with static linking
@SebastianElvis SebastianElvis mentioned this issue Oct 21, 2024
Merged
SebastianElvis added a commit that referenced this issue Oct 21, 2024
@SebastianElvis
chore: bump wasmd and re-enable static linking (#213)
b1a4b48 
Resolves #26 
Also addresses the GH action warning on Dockerfiles

NOTE: `init.Dockerfile` still uses dynamic linking because it builds
v0.9.3. This can only be fixed in the v2 upgrade, unless we release
v0.9.4 with this PR backported (which I don't think it's the case).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SebastianElvis SebastianElvis

Labels
phase-2-readiness
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: bump wasmd and re-enable static linking babylonlabs-io/babylon
2 participants
@SebastianElvis @KonradStaniec