ClouDNS
ClouDNS widens its SSL catalog and adds maintenance windows to monitoring
Comparison · Infra & APIs
nfs-ganesha vs runc
A side-by-side editorial comparison of nfs-ganesha and runc — release velocity, themes, recent moves, and the top alternatives to consider.
nfs-ganesha vs runc: at a glance
What is nfs-ganesha?
NFS-Ganesha's 15.x line turns to weekly fixes, input checks and dropping 9P.
NFS-Ganesha is a userspace NFS server used with Ceph, GPFS and clustered storage. Since 15.3 in early September it has shipped 15.4 through 15.9 roughly weekly. The releases harden XDR decoding against empty handles, owners and strings, fix a session use-after-free and an integer overflow in offset checks, add gRPC QoS APIs for per-client bandwidth and IOPS, and in 15.9 remove the unmaintained 9P protocol code.
What is runc?
runc 1.6.0-rc.1 lifts the 1024-CPU limit and refuses settings it used to quietly ignore
The 1.6.0 cycle opened on October 6 with a first release candidate that is mostly cleanup: deprecated libcontainer APIs removed, Go 1.26 now required, urfave/cli moved from v1 to v3, and the binary about 15% smaller on amd64. The changes with operational weight are that cpuAffinity and NUMA memoryPolicy no longer stop at 1024 CPUs or nodes, and that a container asking for a read-only rootfs without its own mount namespace is now refused. Eleven days earlier 1.5.2 worked around a kernel bug, present since v6.17, that corrupted memory inside runc and caused random crashes on cgroup v2. It also stopped runc exec --cgroup from escaping into a sibling cgroup.
nfs-ganesha vs runc: editorial side-by-side
nfs-ganesha
5.0INFRA · APIS
NFS-Ganesha's 15.x line turns to weekly fixes, input checks and dropping 9P.
◆ Current state
NFS-Ganesha is a userspace NFS server used with Ceph, GPFS and clustered storage. Since 15.3 in early September it has shipped 15.4 through 15.9 roughly weekly. The releases harden XDR decoding against empty handles, owners and strings, fix a session use-after-free and an integer overflow in offset checks, add gRPC QoS APIs for per-client bandwidth and IOPS, and in 15.9 remove the unmaintained 9P protocol code.
◆ Where it's heading
The fast feature run of 15.0 to 15.3 (gRPC management, dynamic config, monitoring) has given way to stabilisation: input validation, Ceph ACL and multi-client fixes, GPFS performance. gRPC continues to grow, with QoS management added in 15.5.
◆ Prediction
Expect more 15.x patch releases on the same cadence. The 9P removal shows a willingness to prune unused code, but the entries do not name other candidates.
runc
2.5INFRA · APIS
runc 1.6.0-rc.1 lifts the 1024-CPU limit and refuses settings it used to quietly ignore
◆ Current state
The 1.6.0 cycle opened on October 6 with a first release candidate that is mostly cleanup: deprecated libcontainer APIs removed, Go 1.26 now required, urfave/cli moved from v1 to v3, and the binary about 15% smaller on amd64. The changes with operational weight are that cpuAffinity and NUMA memoryPolicy no longer stop at 1024 CPUs or nodes, and that a container asking for a read-only rootfs without its own mount namespace is now refused. Eleven days earlier 1.5.2 worked around a kernel bug, present since v6.17, that corrupted memory inside runc and caused random crashes on cgroup v2. It also stopped runc exec --cgroup from escaping into a sibling cgroup.
◆ Where it's heading
The project keeps converting silent behaviour into explicit behaviour. Read-only requests that were ignored now fail, a umask that was dropped is now honoured, and poststart hooks moved to conform to the runtime spec. The same maintainers are shrinking the surface underneath, dropping the deprecated API and the high-level cilium/ebpf path, which took roughly 7.5% off the 1.5.2 binary. Stricter behaviour plus a smaller dependency set is what a component under every container host would be expected to do between majors.
◆ Prediction
1.5.0's notes pointed to a 1.6.0 in late October 2026, and the feed so far shows only rc.1, so further release candidates or the final are the next entries to expect. The refused read-only configurations are the change most likely to surface as user reports during testing.
Alternatives to nfs-ganesha and runc
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either nfs-ganesha or runc.
FOSSA CLI
fossa-cli's feed jumps from 3.17 to 3.20, with clearer container scan errors.
Gloo Gateway
Gloo Gateway's October batch fixes proxies that silently kept stale endpoints.
Traefik
Traefik v3.8 rc.1 is a Gateway API release; v2.11 keeps getting security patches.
Render
Render's autumn changelog is plan tuning and runtime defaults while Workflows fills out.
Home Assistant
Home Assistant keeps pulling hidden power-user features into the UI, now trigger IDs.
See all nfs-ganesha alternatives → · See all runc alternatives →
Recent activity from nfs-ganesha and runc
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 13d agonfs-ganeshaNFS-Ganesha 15.9: 9P removed, session use-after-free fixed
- 24d agonfs-ganeshaNFS-Ganesha 15.8: XDR input checks and GPFS fixes
- 26d agoruncRelease candidate lifts 1024-CPU limit, removes deprecated APIs
- 29d agonfs-ganeshaNFS-Ganesha 15.7: offset overflow fix and GPFS readdir speedup
- 1mo agonfs-ganeshaNFS-Ganesha 15.6: Ceph ACL inheritance and aligned I/O buffers
- 1mo agoruncWorkaround for kernel bug that crashed runc on cgroup v2
- 1mo agonfs-ganeshaNFS-Ganesha 15.5: gRPC QoS APIs and 4096 RDMA connections
- 1mo agonfs-ganeshaNFS-Ganesha 15.4: multiple Ceph clients, monitoring revert
- 3mo agorunctmpfs regression on Ubuntu 20.04 kernels fixed
- 4mo agoruncrunc 1.5.0 stable, with dated support windows for older branches
- 4mo agoruncCVE-2026-41579: /dev symlink host write access fixed
- 4mo agoruncRelease candidate carrying the CVE-2026-41579 fix
Frequently asked questions
What is the difference between nfs-ganesha and runc?
They serve adjacent needs but don't currently overlap on shipped themes. nfs-ganesha is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is nfs-ganesha better than runc?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. nfs-ganesha is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to nfs-ganesha?
Top nfs-ganesha alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "nfs-ganesha alternatives" section above for the current picks, or visit /alternatives/nfs-ganesha for the full list with editorial commentary on each.
What are the best alternatives to runc?
Top runc alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "runc alternatives" section above for the current picks, or visit /alternatives/runc for the full list with editorial commentary on each.