+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Guides, Walkthroughs & Tutorials (https://forum.jellyfin.org/f-guides-walkthroughs-tutorials)
+--- Thread: Update FFMPEG in Docker Command (/t-update-ffmpeg-in-docker-command)
Update FFMPEG in Docker Command - gaming09 - 2023-06-21
Command to update Jellyfin Docker FFMPEG to the latest:
apt update && apt install jellyfin-ffmpeg6 -y
RE: Update FFMPEG in Docker Command - topnomi - 2023-07-10
Wouldn't it make sense for the docker file to be updated to ffmpeg6?
Looking at the GitHub, it looks like a quick change of a jellyfin-ffmpeg5 to jellyfin-ffmpeg6 would make it happen.
I don't have time to figure out how to test that in my setup right now. Currently using docker compose and the official image.
Does anyone have any thoughts?
RE: Update FFMPEG in Docker Command - Shadowghost - 2023-07-11
FFmpeg 6.x support was added in 10.8.10 but we explicitly decided not to upgrade between major FFmpeg versions on a patch release of Jellyfin for stability reasons.
Jellyfin 10.9 will default to use FFmpeg 6.x and you can always manually install it on 10.8.10 and newer.
RE: Update FFMPEG in Docker Command - bitmap - 2023-08-09
If you're using docker-compose you could probably utilize a custom init script to update it automatically when you restart. I'm not sure how other folks start/stop/remove their containers, though.
The LSIO image has custom scripts built in, which makes this super easy and convenient, but it's not hard to do at all yourself, it's the concept of generating an entry point for your container. You would essentially create a bash script compatible with Ubuntu/Debian that runs the apt update/install of whatever you need with all the options (autoremove, etc...) to satisfy dependencies and swap paths if needed. This takes a bit of doing since you have to trial and error it until you're sure the correct version of ffmpeg is running when Jellyfin calls it (i.e., just installing ffmpeg6 may not be the fix you think it is).
The other option is to pull down the repo and modify the Dockerfile, then build it yourself. I don't see this as nearly sustainable or automated, but it's certainly a cleaner solution.