Closed Saroufim closed 3 years ago
Thanks for opening your first issue here! Be sure to follow the issue template!
Libseccomp 2.5.1 or 2.5? 2.5 arrived before 2.4.4 which fixes it for Debian
libseccomp-2.5.0-3.fc33.armv7hl
I will wait for the 2.5.1 update and I will report back.
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.
The lib hasn't been updated yet so I cannot say if it provides the fix or not.
An update was pushed that fixed it.
Expected Behavior
Jellyfin should start normally since libseccomp 2.5 is installed.
Current Behavior
Jellyfin doesn't start after the install script ends. It shows the date as 1970.
Steps to Reproduce
Environment
OS: Fedora IoT CPU architecture: arm32 How docker service was installed: Podman was installed already on the base image and Jellyfin was pulled from Docker Hub.
Command used to create docker container (run/create/compose/screenshot)
podman run -d --security-opt label=disable --name=jellyfin -e PUID=1000 -e PGID=1000 -e TZ=Asia/Beirut -e UMASK_SET=022 -p 8096:8096 /home/user/.jellyfin:/config -v /home/user/media:/data/ --device /dev/vchiq:/dev/vchiq --restart unless-stopped ghcr.io/linuxserver/jellyfin
Docker logs