mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
Fatal glibc error: cannot get entropy for arc4random - with Docker on Synology 7.1.1 #7965
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @KusAdama on GitHub (Dec 30, 2025).
Description of the bug
Using this docker-compose.
The
sudo docker-compose updoes ending all the time with this in logs (entire one run below) for the jellyfin container:The Synology DSM is fairly old on this machine, but maybe someone could push me the right direction.
Reproduction steps
create compose.yml on DSM 7.1.1
run: sudo docker-compose up
What is the current bug behavior?
Never ending restart of container
What is the expected correct behavior?
Could start and be functional
Jellyfin Server version
10.11.5
Specify commit id
No response
Specify unstable release number
No response
Specify version number
No response
Specify the build version
Can't get in the dashboard yet
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Additional information
No response
@ZeusCraft10 commented on GitHub (Dec 31, 2025):
The Correct Fix: Use a "Jammy" Tag
You do not need to build your own image. You simply need to change the Tag you are pulling in Docker.
Instead of latest (which pulls Ubuntu 24.04), explicitly pull a version based on Ubuntu 22.04.
If you use docker-compose.yml: Change this:
YAML
image: jellyfin/jellyfin:latest
To this:
YAML
"10.9.11" is an example; verify the latest version on Docker Hub that supports jammy
LinuxServer.io images often explicitly tag the base OS, e.g., "10.9.9-ubu2204"
image: jellyfin/jellyfin:10.9.11
Note: You may need to look for specific tags provided by the maintainers (like linuxserver/jellyfin) that explicitly support older Ubuntu bases if the official jellyfin/jellyfin repo stops publishing Jammy-based builds for the newest versions.
Summary
@KusAdama commented on GitHub (Dec 31, 2025):
This is some AI generated response.
I'm not even reading it in detail as its formatting is broken and it does not explain anything.
@ZeusCraft10 commented on GitHub (Dec 31, 2025):
I just meant the issue is caused by his older build on the synology. its not in the score of a PR.