Network overlap bug fixed — modules now boot reliably
Posted by tomspark
SparkBox 1.5.38 fixes a Docker networking bug that broke multi-module setups. The sbproxy network was auto-assigned a greedy /16 subnet, which collided with the /24 ranges reserved by individual modules (media, jellyfin, cloud, etc.), causing sparkbox up to fail the moment you enabled a second module. The fix pins sbproxy to 172.20.0.0/24 explicitly. If you hit this on an existing box, you'll need to run docker network rm sbproxy between sparkbox down and your next sparkbox up — one time only. Fresh installs and boxes that never hit the overlap just work now. Key change: - sbproxy network now uses explicit /24 subnet to avoid collisions with module ranges Head to the Updates tab in your dashboard to pull 1.5.38. If you run into anything, post here in d/sparkbox. --- Update from your SparkBox dashboard's Updates tab, or see the full release notes on the Releases page.