Docker container for TVE on Ubuntu. "No such folder" error for dev/dri

When trying to run the TVE fancybits Docker container, I receive the following error on Ubuntu 22.04 on Intel i7 laptop:

Error response from daemon: error gathering device information while adding custom device "/dev/dri": no such file or directory.

But I do see that folder, and there are files in it. I have added my user to the video and render groups.
I changed the permissions on /dev/dri to be 777.
I have tried adding the /dev/dri folder as a resource in Docker desktop.

None of these steps have worked when trying to use the TVE container.

Channels DVR does run as expected if I install it as a Linux application, not inside a Docker. But I use TVE often and so wanted to try to get the Docker version to work.

Any suggestions on how to get Docker to see or have access to that folder?
Thanks.

Remove the part of the docker command that references /dev/dri

Thanks for help. After removing the device parameter, the docker command does run now and starts the container, but I don't see any exposed ports in Docker desktop.
When I go to locahost:8089, it says server not found.

I was able to start the Pluto for Channels Docker successfully. I can see the main page at localhost:8080. So it seems to work for that container.ere

Here is my Docker cli command:

docker run \
  --detach \
  --name=channels-dvr \
  --net=host \
  --restart=on-failure:10 \
  --volume <local path>:/channels-dvr \
  --volume <local path>:/shares/DVR \
  fancybits/channels-dvr:tve

Okay you may need to remove --net and and --port like Pluto does

1 Like

-p 8089:8089

1 Like

That got it. Now I get the welcome and setup page at localhost:8089. Thanks!

and change the two <local path> to actual directories on your server
the first being where it keeps its executable code
the second being where your recordings are written to

1 Like

Thanks for noticing and clarifying that. Yes, I have those local paths set in the actual run command, I'm just hiding the values for posting here.

1 Like

OP is following up in this thread wanting to enable hardware transcoding

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.