# Container can´t access /dev/ttyAMA0

**URL:** <https://forums.balena.io/t/container-can-t-access-dev-ttyama0/350392>\
**Category:** balenaOS\
**Tags:** bluetooth, serial, docker, network\
**Created:** [December 2, 2021, 11:13am UTC](https://forums.balena.io/t/container-can-t-access-dev-ttyama0/350392 "2021-12-02T11:13:09Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Mawiguk0](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/mawiguk0/32/6303_2.png) [@Mawiguk0](https://forums.balena.io/u/Mawiguk0)\
**Post date:** [March 2, 2022, 10:01pm UTC](https://forums.balena.io/t/container-can-t-access-dev-ttyama0/350392/6 "2022-03-02T22:01:45Z")

</div>

hy @mtoman  
thank you for your reply!!!

Indeed the fleet runs on RPi3

I asked the question on my company user account again @Markus.Kohn.GWA

> [@Container can´t access serial Interface to establish BLE Device Resets.](https://forums.balena.io/t/container-can-t-access-serial-interface-to-establish-ble-device-resets/350442/12):
>
> Hi, i granted support access for one week and hope that at least somebody could have a look into this behavior/ situation. Still looking forward to use balenaOS + [balena.io](http://balena.io) for our fleet

Anyway:  
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

Best Regards

Markus

---

_[View the full topic](https://forums.balena.io/t/container-can-t-access-dev-ttyama0/350392)._