fix(docs): repair Docker fullnode guide (stale image, genesis, statesync)#117
Open
cbarraford wants to merge 1 commit into
Open
fix(docs): repair Docker fullnode guide (stale image, genesis, statesync)#117cbarraford wants to merge 1 commit into
cbarraford wants to merge 1 commit into
Conversation
…ync) The Docker fullnode page does not produce a working node as written. Verified by running the documented steps: - Documented image `mainnet-2.135.1` crash-loops: its baked-in Nine Realms seed URL no longer resolves, so it can't self-fetch genesis and fails to start. Bumped to a current tag and added guidance to track the network version. - Genesis is fetched automatically from seed peers; the manual "get genesis from node-launcher" step was non-actionable. Clarified, and noted a genesis fetch alone is insufficient. - A current binary cannot replay from genesis (InitChain panics). Added the StateSync bootstrap path (`THOR_AUTO_STATE_SYNC_ENABLED=true`, verified to reach snapshot discovery) with its RAM requirement, plus a snapshot-restore alternative noting the linked node-launcher doc is Kubernetes/make-based. - Added `--platform linux/amd64` note for arm64 hosts (image is amd64-only). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
The Thornode on Docker fullnode page (
thornodes/fullnode/thornode-docker.md) does not produce a working node as written. I verified this by actually running the documented procedure; this PR fixes it.What I found (empirically)
mainnet-2.135.1crash-loops. Its baked-in seed source is the decommissioned Nine Realms host (api.ninerealms.com/thorchain/seeds), which no longer resolves → no seeds → genesis self-fetch is skipped →couldn't read GenesisDoc file ... no such file→ restart loop./genesis_chunked) by current binaries — the manual "get genesis from node-launcher" instruction is non-actionable, and a successful genesis fetch alone is not enough to join.mainnet-3.18.1) the genesis self-fetch succeeds (40 MB state-export), butInitChainthen panics:panic: invalid addressinx/bank InitGenesis→ crash loop.THOR_AUTO_STATE_SYNC_ENABLED=truechanges the outcome: the node sets a trust height from the default RPC servers and reachesDiscovering snapshotswith 0 restarts and no panic (verified). Completing a statesync needs substantial RAM (~80 GB per node-launcher).make-based with no docker-compatible procedure.--platform linux/amd64.Changes
THOR_AUTO_STATE_SYNC_ENABLED=true, with RAM caveat) and a snapshot-restore alternative (noting the linked doc is k8s/make-based).docker runexample and an arm64--platformnote.Not fully verified
A complete statesync was not run to tip (requires ~80 GB RAM / large disk); verification reached
Discovering snapshots. Maintainers may prefer a different pinned image tag thanmainnet-3.18.1.🤖 Generated with Claude Code