thanks for your report. Just to be sure - do I understand correctly that the device in question is a Raspberry Pi 3? As for the device - I can see your container is privileged, that should mean all the devices are populated inside the container on creation and accessible. So to debug further, could you please check the following:
Can you see /dev/ttyAMA0 on the host OS?
Can you see /dev/ttyAMA0 within the tower container?
Is there any particular error message you are getting from your application?
Im able to see /dev/ttyAMA0 inside hostOs and Tower container.
The problem is:
The software running in the tower container does not use hci. It wants to send its ohn commands to the serial interface/ Bluetooth device.
Which is most likely already in use by another process.
So the goal would be to ensure that nothing else is initializing a bluetooth.service or hciattach beside the tower container
If you’re able to see /dev/ttyAMA0 from host and from inside the container, the issue might be with the software (either trying to acquire multiple locks, or something else?), if you try another container, is it able to communicate with the serial interface?