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

Build a portable stacks-node image #4557

Closed
hugocaillard opened this issue Mar 18, 2024 · 5 comments
Closed

Build a portable stacks-node image #4557

hugocaillard opened this issue Mar 18, 2024 · 5 comments
Assignees
Labels
chore Necessary but less impactful tasks such as cleanup or reorg CI locked

Comments

@hugocaillard
Copy link
Collaborator

The Devnet (clarinet devnet) is used by developer to run a local Bitcoin node, Stacks node, Signer node, and more.
Hence we need to be able to run stacks docker image on any platform.

Currently, the devnet runs linux/amd64 image, even on macos through docker emulation. But it doesn't seem to work anymore on images built from source recently.

@github-project-automation github-project-automation bot moved this to Status: 🆕 New in Stacks Core Eng Mar 18, 2024
@wileyj wileyj added chore Necessary but less impactful tasks such as cleanup or reorg CI labels Mar 18, 2024
@wileyj
Copy link
Contributor

wileyj commented Mar 18, 2024

to add some context, the images are no longer portable due to the inclusion of jemalloc to x64 builds.

@BowTiedDevOps two things we can look at here:

  1. multi-platform build - for each PR, could we build for both x64 and aarch64 (and how much longer would it take to do so)?
  2. disable jemalloc from x64 PR image builds. this might be a little tricky, but i think it's doable

ref:
#4460
#4367

@wileyj
Copy link
Contributor

wileyj commented Mar 18, 2024

on an aarch64 machine, running docker run --platform linux/amd64 blockstack/stacks-blockchain:feat-2.4.x-nakamoto-migration stacks-node mainnet start errors with:

<jemalloc>: MADV_DONTNEED does not work (memset will be used instead)
<jemalloc>: (This is the expected behaviour if you are running under QEMU)
qemu: uncaught target signal 11 (Segmentation fault) - core dumped

@smcclellan
Copy link

@BowTiedDevOps @wileyj Is this issue meant to be closed?

@wileyj
Copy link
Contributor

wileyj commented Jun 20, 2024

yes - this was solved prior to 2.5

@wileyj wileyj closed this as completed Jun 20, 2024
@github-project-automation github-project-automation bot moved this from Status: 🆕 New to Status: ✅ Done in Stacks Core Eng Jun 20, 2024
@blockstack-devops
Copy link
Contributor

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Oct 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
chore Necessary but less impactful tasks such as cleanup or reorg CI locked
Projects
Archived in project
Development

No branches or pull requests

5 participants