tomspark wrote:
Sorry about this one — Immich knocking the other apps over while it installs is not you, that shouldn't happen and it's ours to dig into. Immich is by far the heaviest app we ship, so I want to see exactly where it gives up. Next time you try it, run the install from a terminal so we get the whole story: sudo sparkbox enable immich && sudo sparkbox up Success looks like it finishing with everything green. If it dies partway, copy the last 15 or so lines it printed and paste them here — that'll show me where it's falling over and I'll take it from there.
tomspark wrote:
The green finish is good — but x15 restarts means Immich is crashing right after startup. Let's see why. Run this and paste the last 20 lines: docker logs sb-immich-server 2&1 | tail -20 That'll show us the exact error. Immich is heavy, so if it dies it's usually OOM (not enough RAM) or a DB migration issue — logs will tell us which.
Chris wrote:
Twelve days late, and you can skip those logs — the cause wasn't Immich, and it wasn't your RAM. It was SparkBox's own disk monitor. At 95% full it ran a Docker cleanup that also deleted every stopped container — and mid-install with a full disk, that is exactly what your arr apps were. It re-checks every 30 seconds, so Immich's ~4GB pull kept refilling the disk and the cleanup kept re-firing. That's your media stack breaking while Immich installed. Tom shipped the fix in v1.6.457 — it now reclaims images and build cache only, never containers. sudo sparkbox upgrade sudo sparkbox up That second command recreates anything that was removed; nothing at boot does. Then retry Immich with a few GB spare. — Chris