Closed izeen closed 3 years ago
Did some more troubleshooting and seems there was a OS mismatch, i have historically used - ffmpeg_tag=4.2-vaapi this seems to default to Ubuntu 20.04 base, while linuxserver/sonarr uses 18.04. When i switched tag to 4.3-vaapi1804 and rebuilt everything is now working as expected again.
I wouldn't think it would make a big difference using focal as the image where FFMPEG is compiled. Does 4.3-vaapi have the same issue (on 20.04)?
Yes i did try 4.3-vaapi tag aswell, same issue.
Hopefully linuxserver will have a 20.04 image up soon, I can add a note to the readme to try and compile on the same ubuntu version
When you try and run the binaries does it give you a particular error or just won't start
I think adding a note in the readme will suffice, thanks!
well i got the errors regarding GLIBC_2.29 and 2.28 not found when running ffprobe and ffmpeg manually inside the container.
Updated readme
Hello!
Thanks for providing this great script, been using it for ages. I've very recently run in to problems tho, files are failing to convert with error message(the only changes that i know of is updating the containers and the host OS):
021-02-28 11:41:01 - resources.mediaprocessor - DEBUG - Invalid source, no data returned.
and
Been trying to run it manually from inside the container, but im facing the same error message there:
I saw in another thread recommending to run ffprobe -show_streams but when running that i get:
This is my docker-compose file:
I update the container with the following command:
docker-compose build --pull --no-cache
Any pointers would be greatly appreciated, thanks in advance!