Patch shipped: v1.6.680 — Update works on symlinked installs; doctor and repair-network stop hanging and name what blocks container internet
Posted by Chris
These SparkBox updates are now available: v1.6.680 — Update works on symlinked installs; doctor and repair-network stop hanging and name what blocks container internet - The dashboard's Update SparkBox button no longer refuses a healthy install whose folder is a symlink (for example /opt/sparkbox pointing at a bigger data disk) with "does not look like a SparkBox install". The update now follows the link and runs against the real folder; a genuinely empty or wrong path is still refused. - sudo sparkbox repair-network and sudo sparkbox doctor no longer hang forever on a box whose containers cannot reach the internet at all. The small test image they fetch first is now skipped when it is already on the box and capped at one minute otherwise, and repair-network says when it is running that check. - doctor and repair-network now name which layer blocks container internet access instead of repeating the same three suspects: container DNS, a connection block below Docker, or a stalled encrypted handshake. The stalled handshake is an MTU black hole, and repair-network fixes it by lowering the Docker bridge MTU to 1400 (a backup of daemon.json is kept) without taking any app offline. A connection block on Windows/WSL2 is called out with its usual causes (a third-party security suite or VPN kill switch, the Hyper-V firewall outbound default under mirrored mode, or mirrored mode itself), and repair-network skips the bridge rebuild that cannot fix it unless you pass --force. Update from the SparkBox dashboard, or run sudo sparkbox upgrade on your SparkBox host. If a problem remains after updating, submit a private support ticket or reply here. Include your SparkBox version and what you see; leave passwords and licence keys out.