July-4th-2018, 08:30 AM
Well Frank,
usually if you specify the privileged mode under standard Docker when starting a container then all /dev/ devices are mapped into a container. Not so with netPI's Docker cause of security reasons.
Mapping all devices would mean that also the boot drive of netPI would also get accessible and this is what we do not want, else customers could modify this drive and we would expect many non-working netPIs then. So we restricted Docker at this point.
So with netPI you will have definitively have no other chance other than to map the /dev/ttyUSBx devices manually.
usually if you specify the privileged mode under standard Docker when starting a container then all /dev/ devices are mapped into a container. Not so with netPI's Docker cause of security reasons.
Mapping all devices would mean that also the boot drive of netPI would also get accessible and this is what we do not want, else customers could modify this drive and we would expect many non-working netPIs then. So we restricted Docker at this point.
So with netPI you will have definitively have no other chance other than to map the /dev/ttyUSBx devices manually.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
