-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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]: [OpenVino:] Intel compute runtime required for Frigate #12266
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Unfortunately I have the same problem. Before Update to Ver. 14 ist was no problem.
|
This comment has been minimized.
This comment has been minimized.
The problem occurs for me as well. Unfortunately because I am on Kubernetes I cannot persist container filesystem changes easily so that workaround is not really feasible. The environment variable workaround also does not work. This is on 24.04 and I tested multiple mainline kernels 5.8.0 6.8.0, 6.8.12 all with the same result. Is there an image that has these commands run on the container available? Would a PR that modifies the image with these commands (with errors fixed) be the proper solution or is this a bug that's expected to be solved upstream? |
@DeltaTango69 this does not seem like the issue discussed here, what is your docker config @wernerb The issue that this is referring to will be fixed upstream, but from your description it is not clear if you are actually experiencing the issue being discussed here |
This comment has been minimized.
This comment has been minimized.
It's about a specific error message that occurs due to this missing package. You should make your own support request |
As I understand this is only a temporary solution.The solution should be in my opinion the integration of the new openvino update in the frigate image. |
I'm unclear on how to apply the temporary solution. The stable image uses Debian 11, which doesn't have zst support, so I get an error when trying to install the intel compute runtime: e.g. I get the error message:
Am I missing something obvious? I'm running the container inside Ubuntu 22.04 w/ Meteor-Lake (Intel Core 5 Ultra) docker-compose.yml:
frigate config.yml:
|
Same problem, different install. AMD CPU, Intel ARC 380 GPU. |
@fouticus try to repack it with this script below.
Now we have to repack packages that are packed with zst, I suggest to use script, copy it to file repack.sh
make it executable |
Hi, Thanks |
This should be fixed in dev images |
Thanks, unfortunately it didn't help in my case.
|
you might be seeing a different issue then, the latest dev builds have the latest libraries from intel as marked in the OP |
I can confirm that openvino works - thank you! |
Any chance of getting a patch release on 0.14 for this? Otherwise would there be a recommended most-stable dev image to use in the meantime? |
No, it's a big change that requires beta testing |
Just wanted to note that I'm not experiencing this issue anymore after a kernel update in proxmox to |
@ctml91 what CPU do you have? I am having the same issue with J5005, even on the latest dev Frigate images. |
Discussed in #12260
Originally posted by Redsandro July 2, 2024
Describe the problem you are having
When starting from scratch:
.. the OpenVino detector does not work with the Intel iGPU until the latest Intel Compute Runtime is installed inside the Frigate container:
I am aware that none of the maintainers use OpenVino. The problem and the solution have been observed by myself and at least one other person.
If I understand correctly, Intel Compute is a dependency for OpenVino in Frigate, and it needs to be updated to the latest version in order to use the latest kernel.
I did a search and believe this is not being tracked as a bug yet. My apologies if I missed something.
Steps to reproduce
docker compose down && docker compose up -d
)docker compose logs -f --tail=100
)[GPU] Context was not initialized for 0 device
CPU
in configdocker compose restart
)GPU
in configdocker compose restart
)Version
0.14.0-beta3
Frigate config file
Relevant log output
Operating system
Proxmox
Install method
Docker Compose
Network connection
Wired
Camera make and model
irrelevant
Any other information that may be helpful
This is relevant for both Ubuntu 22.04 and 24.04.
Running
dpkg -i *.deb
above throws an error or two due to certain packages already being installed, but these can safely be ignored. Here is a fix for one package, but I didn't use it.Added: I thought I was creating an
issue
but the issue wizard redirected this back todiscussions
.At least it has the
bug
label now. 🙂The text was updated successfully, but these errors were encountered: