April-19th-2018, 05:40 PM
Hi Patrick,
to be honest this would be the very first time I heard of that a container and its applications installed do not start right after a system boot. This would raise Docker to question if there would be such a basic error.
If you dig deeper into Docker technology you see that all application threads and daemons started in a container are 100% threads in the host linux. So there are no differences who is starting them and I really would wonder why this would happen now with the bluetooth daemon. I have not tested it myself yet on a netPI.
What I can say is that the provided example bluetooth container runs fine on a standard raspberry Pi 3 I have right in front of me. So there is no software problem at all. Also netPI is 100% the same circuit as an original Pi 3, so it can be a hardware issue.
Since the bluetooth container allows you to login from remote using putty what happens in your container when it didn't activate bluetooth and you login with root:root and call "bluetoothctl" in in the shell "scan on". Does it start to scan and output the found bluetooth devices on your console?
Give me time tomorrow to make checks with a netPI and then we will see.
to be honest this would be the very first time I heard of that a container and its applications installed do not start right after a system boot. This would raise Docker to question if there would be such a basic error.
If you dig deeper into Docker technology you see that all application threads and daemons started in a container are 100% threads in the host linux. So there are no differences who is starting them and I really would wonder why this would happen now with the bluetooth daemon. I have not tested it myself yet on a netPI.
What I can say is that the provided example bluetooth container runs fine on a standard raspberry Pi 3 I have right in front of me. So there is no software problem at all. Also netPI is 100% the same circuit as an original Pi 3, so it can be a hardware issue.
Since the bluetooth container allows you to login from remote using putty what happens in your container when it didn't activate bluetooth and you login with root:root and call "bluetoothctl" in in the shell "scan on". Does it start to scan and output the found bluetooth devices on your console?
Give me time tomorrow to make checks with a netPI and then we will see.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
