Cannot map /dev/tty0 to the add-on container

[nisargjhaveri]

Describe the issue you are experiencing

I'm trying to develop an add-on that runs an Xorg server and tries to display using the connected hdmi. The Xorg server needs access to /dev/tty0 in order to start.

After playing around a bit, I figured that access to /dev/tty0 is only possible with full_access and with protection off. I'm not able to map /dev/tty0 using the devices option as mentioned in the docs. When added to devices, nothing happens and the cgroups for the container doesn't seem to be affected at all.

Not completely sure, but maybe this is an effect of us trying to "hide not needed devices" in hide_virtual_device. Would it be possible to add support for mapping /dev/tty* in the add-on without having to fallback to full_access?

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Steps to reproduce the issue

1. Add /dev/tty0 to devices in add-on's config.yaml
2. Build and install the add-on, inspect docker container, notice that the cgroups does not contain information for /dev/tty0

Anything in the Supervisor logs that might be useful for us?

NA

System Health information

NA

Supervisor diagnostics

No response

Additional information

No response