Skip to content

fix: specify platform in docker build#845

Open
NickJ202 wants to merge 466 commits intofeat/community-nodefrom
fix/community-docker-build
Open

fix: specify platform in docker build#845
NickJ202 wants to merge 466 commits intofeat/community-nodefrom
fix/community-docker-build

Conversation

@NickJ202
Copy link
Copy Markdown

Specifies --platform=linux/amd64 for both builder and runtime stages to ensure consistent compilation

speeddragon and others added 30 commits March 4, 2026 19:13
…x to access top via shell as well via release
Now the dev_bundler server manages the dispatch workers directly
Continues the refactoring of the dev_bundler modules and implements functionality to allow unbundled items and unfinished bundles to be recovered incrementally rather than requiring that all data be loaded first before any of it is processed
also force an lmdb flush to disk to ensure recovered items are correctly persisted
…ed regression within this PR)

Now we do 2 converts before posting a TX:
- one to build a Header-only TX that we use for posting. This makes the posting process much quicker
- one to biuld a full-data TX tha we use for caching and recovery

We shouldn't need to cache the full-data TX, so a future optmization can address that. We'll just have to be careful about rebuilding the data payload from the cache data items to ensure the reult is the same as when the original TX was posted
shyba and others added 23 commits April 3, 2026 12:55
Remove verify_data_root guard added in 4603f31 to isolate
the skipcat changes from the data_root_mismatch check.
feat: filtering and sorting by Arweave block height
Swap b64fast (C NIF) for b64rs (Rust NIF, base64-simd).
Same API: encode/1, decode/1. URL-safe no-pad.

https://github.com/permaweb/b64rs
impr: experimental lmdb + no_readahead
Sample LMDB metrics 1% of the time and check ensure_started once per proc
Previously the extract of subdomains from the client provided `host` value was broken for non-subdomain requests. This meant that a request on the node's root would needlessly return a 404 due to failure to resolve the empty string as a name.
`~arweave@2.9` previously incorrectly made the `codec-device` local to the request message of a proxied bundler dispatch. This patch corrects it to be in the global scope, such that it is detected by the `hb_http` flow on the receiving end
fix: correctly extract subdomain from client request and node `host`
fix: Correct bundler path query parameter
- Self-contained setup for running a HyperBEAM community node
- Configurable Arweave node address via env var
- Auto-starts continuous block indexing via cron
- LMDB data persisted in Docker volume
- Add detect-coverage.py to discover indexable block height ranges
- Add start.sh for native startup with continuous indexing
- Add AUTO_INDEX env var to control continuous indexing
- Add guided setup section for AI assistants in README
@samcamwilliams
Copy link
Copy Markdown
Collaborator

Thanks @NickJ202 , but what does that do to the non-x86 behavior? We don't want it to run in compatibility mode. We have encountered this issue before I think and I don't remember if there was a good fix.

@NickJ202
Copy link
Copy Markdown
Author

Thanks @NickJ202 , but what does that do to the non-x86 behavior? We don't want it to run in compatibility mode. We have encountered this issue before I think and I don't remember if there was a good fix.

It should still work, but definitely slower in emulation mode. Maybe we could conditionally check the platform inside the Dockerfile ?

@nikooo777 nikooo777 force-pushed the feat/community-node branch 5 times, most recently from 7099078 to 9160eb3 Compare April 20, 2026 18:04
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.

6 participants