+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Jellyfin container fails to start after update (/t-jellyfin-container-fails-to-start-after-update)
Jellyfin container fails to start after update - robertjdac - 2024-12-30
I've had Jellyfin set up in a Docker container for the past year working with nvidia hardware transcoding without issue.
Today I made the mistake of running Watchtower which updated all my containers. All successfully updated except for Jellyifn.
When it tries to start, I get this error in Portainer:
Failed starting container: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy' nvidia-container-cli: detection error: nvml error: unknown error: unknown
The logs spam the following for a while:
[02:49:33] [INF] [23] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
Any idea what I broke when updating?
Thanks
RE: Jellyfin container fails to start after update - robertjdac - 2024-12-30
I removed the gpu/device passthrough from the docker compose file and jellyfin container does start; however I can't even login to my server anymore. It's like it deleted my user/settings.
Guess I should never run Watchtower.
RE: Jellyfin container fails to start after update - bitmap - 2024-12-30
Quote:Guess I should never run Watchtower.
Yes, please! Watchtower is an absolute nightmare unless you use something like LSIO images pinned to a version number that receive various updates to the base OS. It will absolutely destroy your shit otherwise.
If you want an "update" solution that worked well for me for a number of years, try diun: https://github.com/crazy-max/diun. You get notified when a new version is available (I used Slack and Matrix webhooks while I used it) and can format the message to your liking, even with links to release notes and such. Nowadays I check often enough that I don't really need notifications, plus my server is extremely stable, so I fear introducing instability...
RE: Jellyfin container fails to start after update - robertjdac - 2024-12-30
(2024-12-30, 03:32 AM)robertjdac Wrote: I removed the gpu/device passthrough from the docker compose file and jellyfin container does start; however I can't even login to my server anymore. It's like it deleted my user/settings.
Guess I should never run Watchtower.
Well I was able to get it running again, and logged back in... however, I still can't get the Nvidia transcoding to work. It seems to have completely broken. Now whenever I run "nvidia-smi" from the command line, it just says "NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running."
Not sure why Watchtower would have broken my nvidia drivers... but this was all working and it was a huge pain to set up!
RE: Jellyfin container fails to start after update - TheDreadPirate - 2024-12-30
Reinstall the Nvidia container toolkit?