-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[Support]: Beta11 Can't Find FFMPEG #3223
Comments
This looks like the error that was fixed by 9c4da5a, seems it can't find ffmpeg are you saying this doesn't happen when you remove hwaccel args? looking at the logs it seems this would happen regardless |
Yes, it's happening regardless of the hwaccel args being commented out or not. Before the beta, I just had them commented out. But since installing the beta, I have tried a couple different variations. Am I missing something, wouldn't surprise me. |
Can you confirm which architecture you are on? Were you previously pulling the amd64 image? |
Okay cool, so the title isn't accurate. And no I don't think this is on you, seems something with the docker container. What CPU / arch are you running? If you are able, it would be helpful if you could open a terminal inside the docker container and run |
Correct. I was kind of wondering about that. |
I was previously on 0.10.1-amd64 I am assuming you mean docker container (I run in a proxmox container). When I run |
@blakeblackshear Seems like this may be related to proxmox? So far only proxmox users have reported this issue 🤔 |
Maybe having to do with this: https://jellyfin.org/docs/general/administration/hardware-acceleration.html#va-api-and-qsv-hardware-acceleration-on-lxc-on-proxmox @esmoyer is the container that frigate runs in privileged? |
Looks like what I linked is about hw_accel so may not be it |
I have the same issue, also running in a privileged Proxmox container. When attaching to the docker container I see: If I should provide more information let me know. Thanks for your support and all the work :) |
Ubuntu 20.04 user having same issue "FileNotFoundError: [Errno 2] No such file or directory: 'ffmpeg'" |
@Zunhammer What you have there is not the same issue as this, can tell because ffmpeg is found it is just crashing with hw_accel args. |
@Zunhammer I would recommend creating your own issue as we don't want to add clutter for those that are experiencing the ffmpeg not found issue. |
Can someone post the output of |
|
ffmpeg is at /usr/lib/jellyfin-ffmpeg/ffmpeg in blakeblackshear/frigate:0.11.0-beta2 container. |
Yea. That's not right. The dockerfile clearly sets the PATH environment variable. Something is overwriting that value in the container. |
Interesting. Want me to try doing a fresh install or anything else? |
That did it. My container had “PATH” Environment variable set same as @esmoyer posting above. I delete the “PATH” variable using portainer and restart container and issue is fixed. |
Yep, just did the same thing and seems to be working now. |
I had the same issue using portainer, environment path value was wrong. Originally my portainer was pulling blakeblackshear/frigate-amd65, now everything works without issue or editing after changing pull blakeblackshear/frigate |
Describe the problem you are having
Looks like I'm getting green screens with the new beta build, which I assume is due to what you mentioned as I have not changed anything else with moving to the beta. Excited to get it going!
EDIT: Sorry my stats kept pasting weird. Let me know if you need more or other info!
Version
0.11.0-beta2
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Operating system
Proxmox
Install method
Docker Compose
Coral version
USB
Network connection
Wireless
Camera make and model
Amcrest AD410 and Eufy C22
Any other information that may be helpful
No response
The text was updated successfully, but these errors were encountered: