This bug looks to me either a wontfix or provide a better documentation on how to fine-grain configure docker for LAVA use cases.
IMO, a better approach would be to deny direct access to devices and recommend to use "bridge" tools like ser2net or adb over tcp, which rely on networking and would be easier to configure.
As long as you need to access to host devices (e.g. USB), you need to run in privileged mode or use a fine-grained configuration: https://docs.docker.com/engine/reference/run/#/runtime-privilege-and-linux-capabilities
This bug looks to me either a wontfix or provide a better documentation on how to fine-grain configure docker for LAVA use cases.
IMO, a better approach would be to deny direct access to devices and recommend to use "bridge" tools like ser2net or adb over tcp, which rely on networking and would be easier to configure.