2024-03-18, 11:30 PM
(This post was last modified: 2024-03-18, 11:31 PM by TheDreadPirate. Edited 1 time in total.)
(2024-03-18, 11:22 PM)matchaman Wrote: It seems that the new docker image is working well with minimal skipping/stuttering, but I am now having an issue where whenever I stop the docker container, it resets the jellyfin server to a like-new setup, making me reconfiugre everything. How do I fix that issue?
It sounds like you didn't provide a volume for the container to write /config to. /config is where Jellyfin writes all of its persistent data to. You also need to provide a volume for Jellyfin to write /cache to so Jellyfin doesn't have to regenerate that after each restart. Both should be on a NVMe volume.
(2024-03-18, 11:22 PM)matchaman Wrote: Is there a fix for the Windows 11 OpenCL driver issue, or one being worked on, or would adding a graphics card help fix the issue? Or what is the best method of hosting the jellyfin server? On bare linux? Or does that require a lot of conifig with drivers as well?
You can revert the Windows Intel driver to one of their November or December 2023 driver releases. I believe their January 2024 driver is the first to have this issue.
The best method for hosting Jellyfin is the one you are comfortable with managing. Each platform has its benefits and drawbacks.
Jellyfin 10.10.1 (Docker)
Ubuntu 24.04 LTS
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)
![[Image: GitHub%20Sponsors-grey?logo=github]](https://img.shields.io/badge/GitHub%20Sponsors-grey?logo=github)
Ubuntu 24.04 LTS
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)