Hardware and VPS Sizing
Choosing the right amount of RAM, CPU, and storage upfront avoids painful resizing operations later.
What this page covers
- Minimum and recommended specs for single-node Docker deployments
- Minimum and recommended specs for a K3s single-node and multi-node cluster
- Disk sizing considerations for container images, volumes, and backups
- When to add a second node
Quick reference
| Deployment | RAM | vCPU | Storage |
|---|---|---|---|
| Docker-only (minimal) | 4 GB | 2 | 40 GB |
| Docker-only (recommended) | 8 GB | 4 | 80 GB |
| K3s single-node (minimal) | 8 GB | 4 | 80 GB |
| K3s single-node (recommended) | 16 GB | 8 | 160 GB |
| K3s multi-node (per node) | 8 GB | 4 | 80 GB |
Storage notes
- Container image cache grows over time; plan for at least 20 GB dedicated to Docker/containerd storage.
- Persistent volumes for Gitea, YouTrack, and databases need separate consideration.
- Longhorn (K3s track) replicates volumes across nodes — factor in the replication overhead.