November-7th-2017, 03:24 PM
Thomas, your are right. I took my debug netPI now and indeed there is a bluetoothd service started by the Linux host.
After discussing this issue with the development team we came to the common decision that starting the service on the host makes no sense and needs to be removed in the next image version. With Wifi this is different since
If I stop the service on the host I am not getting "binding L2CAP socket: Address already in use" message any longer in the container.
After discussing this issue with the development team we came to the common decision that starting the service on the host makes no sense and needs to be removed in the next image version. With Wifi this is different since
If I stop the service on the host I am not getting "binding L2CAP socket: Address already in use" message any longer in the container.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
