-
-
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
nginx error 12: Cannot allocate memory #1706
Comments
It's probably some kind of issue with the custom nginx build that is not compatible with the Coral Dev board. This happened once for another dependency. It's virtually impossible for me to track down without having a dev board. |
Right on, is there anything I can do to lend a hand, given that I have a dev board? |
My best guess is that something needs to change here: https://github.com/blakeblackshear/frigate/blob/release-0.9.0/docker/Dockerfile.nginx |
Sounds good, I'll take a look. |
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. |
+1 |
maybe the memory is allocated by VOD on the coral-dev-board since 0.9x. |
Does anyone know if this has been fixed? I am keen to try frigate, but the only corals I can find are dev boards. GRRR global chip shortage |
up to now unchanged, i guess.
|
Thanks. |
I'm also hitting this but with a USB Coral on the latest stable frigate.
|
I'm getting the exact same trying to do this without a Coral, only CPU. |
Describe the bug
Frigate
9.0+
is failing to start due to annginx
related memory error on my Google Coral Dev Board. Frigate8.4
runs fine. This is my first attempt at frigate so I apologize if this was caused by a minor oversight.Version of frigate
frigate:0.9.0-rc2-aarch64
Config file
Frigate container logs
FFprobe from camera
Computer Hardware
Camera Info:
640x360
streamAdditional context
I am starting Frigate from a docker container using the following
docker-compose
config:My
/etc/docker/daemon.json
file is as follows:The text was updated successfully, but these errors were encountered: