Developer Edition

[Armin@netPI]

as you've told us (e.g. we can't access all the /dev devices)

This is not correct.

I told you that you cannot map drive devices in general. So mapping the SD card host system image and the bootloader located on /dev/mmcblk0 you cannot map. All other devices can be mapped as on a standard RPi3. There is no need to neither read or write this part of the SD card. In the coming image we will allow mapping also all storage devices that are of type USB ... except drive /dev/mmclbk0 still.

This restriction is not realized with some Docker config settings as you supposed ... since we compile Docker with our Yocto project ourselves from its git hub project we modified the source code. Else you have not chance to realize such modifications.

And still there is no need to know which applications are running next to Docker on netPI. Your world are the containers only. One thing in addition. If you remove from all our netPI Docker examples on Docker Hub the cross compile section for compiling ARM code then Docker Hub would compile x86 code during the automatic build process... and believe me using Kernel 4.9 on any Intel or AMD platform these container would run all the same as on netPI. Cause it is a matter of the Kernel.