SELinux & openVINO

[nhaas1234]

I have Tumbleweed setup with Docker, OpenVino, and Frigate. Everything works Great! Works better than having a Google Coral TPU. On the same hardware, with Google TPU this was a bare metal install (Ubuntu) and openVino is with Proxmox under a tumbleweed VM. ! The only issue I have is when I reboot i need to tell SELinux to allow openVino to work.

So I need to runt these commands:

sudo semodule -i openvino.pp
sudo docker restart portainer

After this, NO ISSUES, until the next reboot.
I have two questions:

1. How do I make this SELinux command permanent?
2. How do I report this to be fixed?

Thank you!

[marel]

AFAIK a change with semodule -i is permanent.

Can you check after a reboot with semodule -l if openvino is still in the list?

[nhaas1234]

openvino is NOT on the list, now that I have rebooted I cant even start openvino at all.

gumeshoetech@localhost:~> sudo semodule -i openvino.pp
[sudo] password for root:
libsemanage.map_compressed_file: Unable to open openvino.pp. (No such file or directory).
libsemanage.semanage_direct_install_file: Unable to read file openvino.pp. (No such file or directory).
semodule: Failed on openvino.pp!

[fkrueger]

@nhaas1234

I have Tumbleweed setup with Docker, OpenVino, and Frigate. Everything works Great! Works better than having a Google Coral TPU. On the same hardware, with Google TPU this was a bare metal install (Ubuntu) and openVino is with Proxmox under a tumbleweed VM. ! The only issue I have is when I reboot i need to tell SELinux to allow openVino to work.

So I need to runt these commands:

sudo semodule -i openvino.pp
sudo docker restart portainer

After this, NO ISSUES, until the next reboot.
I have two questions:

1. How do I make this SELinux command permanent?
2. How do I report this to be fixed?

Thank you!

Just open a bug report according to openSUSE:Bugreport SELinux - openSUSE Wiki.

[nhaas1234]

I will, thank you