Pi Network Node
Pi Network Node is an Unraid Docker template that runs the official Pi Network node on mainnet with performance tuning baked in, significantly reducing CPU…
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
45/100 Fair
- Maintained
- 84last commit 10 days ago
- Popular
- 00 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- 304 GB minimum RAM
Availability: platform listings confirmed today, links checked 27 days ago
- GitHub stars
- 0
- Open issues
- 0
- Last commit
- 2026-11-11
- License
- MIT
- Activity
- declining
Checked 9 days ago - source: GitHub (bitcryptic-gw/unraid-pi-network-node)
Resources & Compatibility
Minimum requirements: 4 GB RAM, 2 CPU core(s), 60 GB disk. ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Setup requirements Map a host path to /opt/stellar for persistent data (required). Standard Pi Network ports: 31401 → 8000 (Horizon HTTP), 31402 → 31402 (stellar-core peer), 31403 → 1570 (local history server). source
- Required host path and ports The template maps a host path to /opt/stellar (required for persistent mode). It exposes three ports: 31401→8000 (Horizon HTTP), 31402→31402 (stellar-core peer), 31403→1570 (local history server / webfsd). source
- Pi Network Node Setup The node needs a host path mapped to /opt/stellar for persistence; the template exposes ports 31401 (Horizon HTTP), 31402 (Stellar-core peer), and 31403 (local history server). source
Fetched 15 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
What must I map and set before starting the Pi node container?
Map a host path to /opt/stellar so the node can persist its data, and set POSTGRES_PASSWORD because the node's Postgres instance requires it.
Which ports does the Unraid template expose?
The template maps 31401 to Horizon HTTP and 31402 to stellar-core peer traffic. It also documents 31403 for the local history server, but only 31401 and 31402 are mapped by the template.
How does the template reduce CPU and host load?
It disables periodic full ledger state verification, limits Horizon ingestion to one worker, and retains about eight weeks of history instead of the full history. These settings are applied through environment variables in the wrapper image.
How do I reuse an existing Pi node identity?
Set NODE_PRIVATE_KEY only when migrating an existing node, and leave it blank for a new node so the container generates one. Do not run two nodes with the same private key at the same time.
What should I check if the node remains stuck at 1?
A node stuck at 1 may still be downloading the ledger in the background, or it may be having trouble finding sources.
Answers sourced from github.com, www.reddit.com
Community
- Pi node : r/PiNetwork - Reddit (reddit)
- PiNetwork - Reddit (reddit)
- Pi network community (other)
Collected 53 days ago - public community threads