September-12th-2019, 08:41 AM
Well David,
as you know Docker on netPI is more restricted than on standard RPi3 in terms of not allowing auto-"/dev"-mapping in privileged mode and not allowing volume bind mappings. So it could be that something more is needed.
The only method I can recommend is to use the tracing tool "strace". You can install it using "apt-get install strace". After installing it you can call "strace -f <your application>" and it prints on screen what Linux systems calls are made by this application and you also see at which point of the calls it fails.
Usually you see then what it is complaining about.
But let me ask you this. On your standard Raspberry Pi ... are you using Raspbian Full with a HDMI Desktop with mouse and keyboard or are you using a Raspbian Lite?
Thx
Armin
as you know Docker on netPI is more restricted than on standard RPi3 in terms of not allowing auto-"/dev"-mapping in privileged mode and not allowing volume bind mappings. So it could be that something more is needed.
The only method I can recommend is to use the tracing tool "strace". You can install it using "apt-get install strace". After installing it you can call "strace -f <your application>" and it prints on screen what Linux systems calls are made by this application and you also see at which point of the calls it fails.
Usually you see then what it is complaining about.
But let me ask you this. On your standard Raspberry Pi ... are you using Raspbian Full with a HDMI Desktop with mouse and keyboard or are you using a Raspbian Lite?
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
