The requirements for a target server named Docker and the .env, but no size. This adds the minimum: 4 GB of RAM.
Changes
README.md, "On every target server": at least 4 GB of RAM. The line gives the measured footprint and points to netOrk's docs/TECHNICAL_DESIGN.md, "Worker memory", for the breakdown per container.
Documentation only. Measured on 172.22.8.50 (74 devices) on 2026-10-08: netOrk's containers take about 2.4 GB, and at least 0.9 GB stayed free after the #752 fixes.
## Summary
The requirements for a target server named Docker and the `.env`, but no size. This adds the minimum: 4 GB of RAM.
## Changes
- `README.md`, "On every target server": at least 4 GB of RAM. The line gives the measured footprint and points to netOrk's `docs/TECHNICAL_DESIGN.md`, "Worker memory", for the breakdown per container.
## Related Issue
NetOrk/netork#752
## Testing
Documentation only. Measured on 172.22.8.50 (74 devices) on 2026-10-08: netOrk's containers take about 2.4 GB, and at least 0.9 GB stayed free after the #752 fixes.
The requirements named Docker and the .env but no size. netOrk's own
containers take about 2.4 GB on a test server with 74 devices, and at least
0.9 GB stayed free once netOrk#752 was fixed. Less than 4 GB leaves no room
for a large task. The breakdown per container lives in netOrk's
docs/TECHNICAL_DESIGN.md, "Worker memory".
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
The requirements for a target server named Docker and the
.env, but no size. This adds the minimum: 4 GB of RAM.Changes
README.md, "On every target server": at least 4 GB of RAM. The line gives the measured footprint and points to netOrk'sdocs/TECHNICAL_DESIGN.md, "Worker memory", for the breakdown per container.Related Issue
NetOrk/netork#752
Testing
Documentation only. Measured on 172.22.8.50 (74 devices) on 2026-10-08: netOrk's containers take about 2.4 GB, and at least 0.9 GB stayed free after the #752 fixes.