-
-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider add ldconfig before starting the jellyfin server #57
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
I'm not sure why you need ldconfig for and which symlinks you are referring to? You haven't added any volume mounts for /config or movies/series, so not sure how you are able to play anything as you don't have a library. Are you running arm or x86_64? Your info is conflicting. |
Oh, sorry that I ignored the volume mounts, because it is too long. Here is the full start.sh command to update the jellyfin docker.
|
Run nvidia-smi on the host |
Running
However, running in docker fails, if entrypoint does not contain
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
please do not close this issue. ldconfig is indeed needed for Nvidia docker 2. |
I'm not sure it is needed (unless I'm missing something) |
After investigating for a while, I think this is actually nvidia-docker's issue (NVIDIA/nvidia-docker#1163 (comment)). When starting the nvidia-docker, the runtime will call host's Closing this issue because it is not good to call |
If you are new to Docker or this application our issue tracker is ONLY used for reporting bugs or requesting features. Please use our discord server for general support.
When using NVENC for hw acceleration, container does not automatically create symlink inside. Users should manually run
docker exec -it jellyfin ldconfig
. This makes auto updating running container base image somewhat not that elegant.Expected Behavior
Directly start container and hw acceleration will work normally.
Current Behavior
Manually create symlink inside the container.
Steps to Reproduce
Environment
OS: Linux omv 5.6.0-0.bpo.2-amd64 #1 SMP Debian 5.6.14-2~bpo10+1 (2020-06-09) x86_64 GNU/Linux
CPU architecture: arm64
How docker service was installed: docker run
Command used to create docker container (run/create/compose/screenshot)
Docker logs
The text was updated successfully, but these errors were encountered: