May-13th-2019, 10:51 AM
Hey Armin,
we now think about two solutions to the problem.
1) Try to get a docker-container with UDEV running in this context of restricted-privileged mode. I assume that sysfs is not accessible in this scenario?
2) You could update the firmware with a modified udev rule system for usb-devices to be mapped in a subfolder of /dev/ like /dev/usb which would allow docker to safely mount the device folder for usb devices, without compromising the whole fs. It may also be possible that way to add dynamic udev/udev-like functionality to the docker container with that.
we now think about two solutions to the problem.
1) Try to get a docker-container with UDEV running in this context of restricted-privileged mode. I assume that sysfs is not accessible in this scenario?
2) You could update the firmware with a modified udev rule system for usb-devices to be mapped in a subfolder of /dev/ like /dev/usb which would allow docker to safely mount the device folder for usb devices, without compromising the whole fs. It may also be possible that way to add dynamic udev/udev-like functionality to the docker container with that.