docker
uinput created devices are inaccessible
So using uinput to create a virtual device is inaccessible if the device is created from inside docker.
What works, passing a /dev/input/* device via --device, this works.
What does not work, creating the device from inside docker (uinput), we do not see it. With --privileged we see it, but cannot open it/read from it.
Please provide more information as requested in the issue-template that was shown when you opened this issue.
- provide the output of
docker version - provide the output of
docker info - provide the exact steps to reproduce. If the steps to reproduce require custom images, or source code, provide a minimal test-case to reproduce. Keep in mind that we don't have access to your private images or source code. Without steps to reproduce, or a reproducible case it's unlikely that your issue can be resolved.
I had a conversation on IRC about this, it seems this is a feature and a hard one to implement at that. The basic idea is to allow hot plug on input devices to RUNNING docker containers. There is no "plumbing" in that regard coded yet.
Also I am not ignoring your request for information because it happens currently to all docker versions. Steps to reproduce are impossible because you cant even do this yet. Using --device to pass through an input device works, but if you hotplug the input device it wont appear until later and the container is already running.
I would like to try to run https://github.com/loki-47-6F-64/sunshine in a docker container, but it requires the creation of uinput devices
