m1k1o / neko

A self hosted virtual browser that runs in docker and uses WebRTC.
https://neko.m1k1o.net/
Apache License 2.0
7.77k stars 570 forks source link

How can I tell if I have VAAPI working? #194

Open GabrielSerealia opened 2 years ago

GabrielSerealia commented 2 years ago

I'm running Neko in an LXC on Proxmox. I've got the /dev/dri mounted to LXC and the docker instance and I have the env var for VAAPI configured.

I'd like to know if there's a way I can check if the hardware encoding is working.

version: "3.4" services: neko: image: "m1k1o/neko:latest" restart: "unless-stopped" shm_size: "2gb" volumes:

m1k1o commented 2 years ago

If you have set NEKO_HWENC=VAAPI what you have, an neko is not failing with:

PNC unable to create video pipeline error="no element \"vaapih264enc\"" module=remote

So it should be working.

Adding - /dev/dri:/dev/dri as devices should be sufficient, no privileged: true needed.

GabrielSerealia commented 2 years ago

Sorry are you saying the config file is correct? Or that I should change "NEKO_HWENC: VAAPI" to "NEKO_HWENC=VAAPI"? The reason I'm asking is because if I don't have - /dev/dri:/dev/dri neko still seems to launch?

m1k1o commented 2 years ago

You either have them all as map with key: value or list with key=value, that is docker-compose yaml spec.

GabrielSerealia commented 2 years ago

Ah, that's what you mean. Thanks!

GabrielSerealia commented 2 years ago

If you have set NEKO_HWENC=VAAPI what you have, an neko is not failing with:

PNC unable to create video pipeline error="no element \"vaapih264enc\"" module=remote

So it should be working.

Adding - /dev/dri:/dev/dri as devices should be sufficient, no privileged: true needed.

So I tried removing the /dev/dri:/dev/dri line in the compose file but neko still seems to run without issue? Are you sure it would spit out that error message if hardware encoding was configured incorrectly?