Open GabrielSerealia opened 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.
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?
You either have them all as map with key: value
or list with key=value
, that is docker-compose yaml spec.
Ah, that's what you mean. Thanks!
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, noprivileged: 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?
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: