[WARN] Hardware Transcoding is set to 'auto' but sb-immich-server was created WITHOUT GPU
Posted by franciscus
My question: [WARN] Hardware Transcoding is set to 'auto' but sb-immich-server was created WITHOUT GPU access -- it is software transcoding (on Jellyfin this surfaces as "Playback failed due to a fatal player error"; on Tdarr as failed GPU transcodes) The overlay is only layered in when the container is CREATED, so a running container keeps whatever it was born with. Fix: sudo sparkbox up immich (recreates it with /dev/dri attached) Then re-run: sudo sparkbox doctor SparkBox AI replied: Yeah, that confirms it. Everything we checked by hand says the device is attached and correctly configured — but doctor is still throwing the same warning verbatim. That's doctor's check being wrong, not your box. Since this is a mismatch in SparkBox's own diagnostic code (not a config issue on your end), I'm not going to keep sending you in circles re-running up. Click "Share to demox" below with this thread — it's got the exact repro (device confirmed attached via docker inspect, env confirmed set, fresh container timestamp, doctor still false-positives) so Tom's team can fix the check itself. Practically: your Immich hardware transcoding is very likely already working fine — ignore that warning for now. If you actually hit a real transcode failure (not just the doctor warning), paste me those logs and we'll dig in for real. What I still need help with: (describe what didn't work or what's still broken)
2 replies
Chris wrote:
Hey franciscus -- good find, and you didn't do anything wrong here. I checked doctor's code myself: for Immich (and a couple other apps) its GPU check looks for one specific signal that never gets set for those apps even when the GPU is attached and working -- so it warns every single time, whether transcoding is actually fine or not. Since you already confirmed the device is attached and set up correctly, your hardware transcoding is almost certainly working. I've flagged this so Tom's team can fix the check itself. If you ever hit a real failed transcode (not just this warning), come back with the logs and we'll dig in.
franciscus wrote:
I will thanks