2024-12-30, 03:07 AM
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
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