Can't run anything besides dashboard after NAS install

Posted by 1ye

My question: From sudo docker version --format 'Client={{.Client.Version}} Server={{.Server.Version}}':Client=29.6.2 Server=29.6.2; from sudo docker info --format 'Driver={{.Driver}} Architecture={{.Architecture}} Kernel={{.KernelVersion}}': Driver=overlay2 Architecture=aarch64 Kernel=6.1.115+ SparkBox AI replied: That fills in the remaining details: text Docker 29.6.2 Storage driver: overlay2 Architecture: aarch64 Kernel: 6.1.115+ The host is ARM64 and Docker is using overlay2, while the underlying pool is Btrfs. The pool stats are clean after reboot, but the same Byparr ARM64 layer still fails with: text tls: bad record MAC So this is no longer pointing at a normal SparkBox configuration problem. It’s a repeatable failure downloading one specific large GHCR blob. The earlier Docker/Btrfs blocking was real, but it isn’t currently recurring. I wouldn’t keep retrying it. Click Share to demox and include: - Docker client/server: 29.6.2 - Driver: overlay2 - Architecture: aarch64 - Kernel: 6.1.115+ - Successful FlareSolverr pull - Failed Byparr ARM64 pull - Clean btrfs device stats - The earlier dockerd blocked / btrfssync messages Tom needs to check the Byparr ARM64 image path or the UGOS/Docker combination here. The evidence is solid enough to escalate, but it doesn’t prove whether the bad data comes from GHCR’s CDN or Docker’s layer handling. What I still need help with: (describe what didn't work or what's still broken Though most apps pull finely, one does not and the dashboard runs empty. Is it possible for me to even run SparkBox ? …(reply truncated — full chat sent to Tom)

2 replies

Chris wrote:

Yes — SparkBox can run on this NAS, and your Docker/ARM64 details do not by themselves point to an unsupported installation. The useful signal is the repeated tls: bad record MAC while downloading the Byparr ARM64 layer: that means the image transfer is being corrupted on the network path, which can leave the dashboard present while the app image is missing. Please do not reinstall SparkBox, Docker, or the NAS data. For the one next check, connect the NAS directly to the router with a different Ethernet cable, then retry the Byparr image pull from the dashboard. If it succeeds there, the NAS and SparkBox installation are fine and the original cable/network path is the cause; if it fails again, reply with only the exact final pull error. SparkBox 1.6.726 now identifies this specific transfer failure instead of suggesting a reinstall, but it does not make a damaged network path reliable.

Chris wrote:

I’m following up on the download failure you described: did the Byparr pull succeed when the NAS was connected directly to the router, or did the same tls: bad record MAC error remain? I also need to correct my earlier conclusion: a different cable test would not by itself prove the original network path was the cause. Please share only the final pull result; don’t reinstall or retry repeatedly.