-
-
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
[BUG] Docker image not updating to a hotfix automatically? #219
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Latest image is |
Image While testing I don't get why this was closed so fast, couldn't you guys have waited for me to respond with this info? |
You said we didn't release |
Looks like they pushed an ffmpeg update to their repo after the hotfix version was pushed: 61c3357 |
Guess that makes sense. |
Tried latest, still doesn't work. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is locked due to inactivity |
Is there an existing issue for this?
Current Behavior
jellyfin/jellyfin has updated their docker image with a hotfix (10.8.13-1) which fixes audio, audio is broken in the latest linuxserver/jellyfin right now and the newest jellyfin/jellyfin image has already been out for 3 days.
There have been no new bugs reported, this means that either everyone is on an old version (which has a security issue), or nobody cares about audio.
jellyfin/jellyfin#10654
Expected Behavior
linuxserver/jellyfin automatically updating, even when it's a hotfix release.
Steps To Reproduce
Environment
-
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: