# After updating balena OS, bluetoothctl can not be used **URL:** \ **Category:** balenaOS\ **Created:** [July 11, 2019, 1:51am UTC](https://forums.balena.io/t/after-updating-balena-os-bluetoothctl-can-not-be-used/18868 "2019-07-11T01:51:24Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![t.higashi](https://avatars.discourse-cdn.com/v4/letter/t/ea666f/32.png) [@t.higashi](https://forums.balena.io/u/t.higashi)\ **Post date:** [July 11, 2019, 1:51am UTC](https://forums.balena.io/t/after-updating-balena-os-bluetoothctl-can-not-be-used/18868/1 "2019-07-11T01:51:24Z")
When updating to Balena OS v2.38.0 of raspberry pi3, Bluetooth dongle can not be used as a controller with bluetoothctl at service of multicontainer application. Originally, v2.32.0 was able to use with bluetoothctl. I believe the following changes in BalenaOS are affecting, but I’m not sure. > docker-compose.yml ```auto version: '2' volumes: resin-data: services: service1: build: ./service1 labels: io.balena.features.kernel-modules: '1' io.balena.features.firmware: '1' io.balena.features.dbus: '1' privileged: true network_mode: host service2: build: ./service2 depends_on: - service1 labels: io.balena.features.balena-socket: '1' io.balena.features.kernel-modules: '1' io.balena.features.firmware: '1' io.balena.features.dbus: '1' io.balena.features.supervisor-api: '1' privileged: true network_mode: host volumes: - 'resin-data:/var/lib/bluetooth' ``` How can I use bluetoothctl？ ---
**Author:** ![hedss](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/hedss/32/210_2.png) [@hedss](https://forums.balena.io/u/hedss)\ **Post date:** [July 11, 2019, 10:13am UTC](https://forums.balena.io/t/after-updating-balena-os-bluetoothctl-can-not-be-used/18868/5 "2019-07-11T10:13:07Z")
Hi there, Thanks for getting in touch. We’d like to try and determine exactly what may be causing this, and have determined there was a Bluetooth change post `v2.36.0`. Could you please try version `v2.36.0+rev2` on your device and see if this works or not. This will help us narrow down what may be happening. Best regards, Heds ---
**Author:** ![t.higashi](https://avatars.discourse-cdn.com/v4/letter/t/ea666f/32.png) [@t.higashi](https://forums.balena.io/u/t.higashi)\ **Post date:** [July 12, 2019, 7:01am UTC](https://forums.balena.io/t/after-updating-balena-os-bluetoothctl-can-not-be-used/18868/7 "2019-07-12T07:01:16Z")
Thank you for your reply. I tried it with Balena OS v2.36.0, but I could not use bluetoothctl. I think that the cause is that the host OS’s systemd bluetooth service grabs the Bluetooth dongle attached to the device. I want to know how to get the container’s bluetooth service, not the Host OS. ---
**Author:** ![thgreasi](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/thgreasi/32/454_2.png) [@thgreasi](https://forums.balena.io/u/thgreasi)\ **Post date:** [July 12, 2019, 11:13am UTC](https://forums.balena.io/t/after-updating-balena-os-bluetoothctl-can-not-be-used/18868/10 "2019-07-12T11:13:05Z")
Thanks for the extra details. We have passed this internally and will get back to you soon. ---
**Author:** ![lucianbuzzo](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/lucianbuzzo/32/615_2.png) [@lucianbuzzo](https://forums.balena.io/u/lucianbuzzo)\ **Post date:** [July 30, 2019, 12:50pm UTC](https://forums.balena.io/t/after-updating-balena-os-bluetoothctl-can-not-be-used/18868/16 "2019-07-30T12:50:21Z")
Hi, we’d like to try and reproduce this issue internally. Would you be able to provide a minimal reproduction of the issue, perhaps as a public GitHub repo or something similar? ---
**Author:** ![sankyo.toshio](https://avatars.discourse-cdn.com/v4/letter/s/46a35a/32.png) [@sankyo.toshio](https://forums.balena.io/u/sankyo.toshio)\ **Post date:** [August 5, 2019, 6:22am UTC](https://forums.balena.io/t/after-updating-balena-os-bluetoothctl-can-not-be-used/18868/18 "2019-08-05T06:22:35Z")
Sorry, for delay. I am a colleague of t.higashi. I will answer instead. We apologize for not showing git repo. But We provide as much information as possible. Our Docker baseimage is `resin/raspberrypi3-buildpack-deps:stretch`. And, Such code is written in Dockerfile of the container in the top question, we need to install bluez. ```auto RUN apt-get update && \ apt-get install -y --no-install-recommends \ bluez \ ``` We will try to do Bluetooth pairing with `bluetoothctl` command with some option in the container. And the following differences are seen by OS. ### balenaOS 2.32 or less - Bluetoothctl is started on the container and the pairing information is displayed. - Pairing information is output to `/var/lib/bluetooth` on the **container side**. - The pairing information is **not** output to `/var/lib/bluetooth` on the **host side**. ### balenaOS 2.36.0 + rev2 or more - Bluetoothctl starts on the container, but the pairing information is not displayed. - Pairing information is **not** output to `/var/lib/bluetooth` on the **container side**. - The pairing information is output to `/var/lib/bluetooth` on the **host side**. ---
**Author:** ![afitzek](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/afitzek/32/359_2.png) [@afitzek](https://forums.balena.io/u/afitzek)\ **Post date:** [August 5, 2019, 2:20pm UTC](https://forums.balena.io/t/after-updating-balena-os-bluetoothctl-can-not-be-used/18868/19 "2019-08-05T14:20:17Z")
Hi, I just tried to reproduce the problem on our side. I used the following Dockerfile as a simple test case. ```auto FROM resin/raspberrypi3-buildpack-deps:stretch RUN apt-get update && \ apt-get install -y --no-install-recommends \ bluez ENTRYPOINT ["/bin/bash"] ``` When running `DBUS_SYSTEM_BUS_ADDRESS=unix:path=/host/run/dbus/system_bus_socket bluetoothctl` in the resulting container and in the interactive shell the commands `scan on` + `connect
` + `pair
` works just fine on balenaOS 2.38.0+rev1. Also `info
` works fine. The `/var/lib/bluetooth` folder in the container is not populated. I tried the same procedure with the same Dockerfile on balenaOS 2.32.0+rev1 and it was the exact same behaviour. There is no `/var/lib/bluetooth` folder in the container, but bluetoothctl works just fine. bluetoothctl communicates via DBUS with the host OS daemon, and the host OS daemon stores it’s state in `/var/lib/bluetooth` you should not install or run your own bluetooth daemon in the container. I’m afraid without a concrete example that reproduces your issue, we won’t be able to help you. We don’t need to see your application code, just the smallest possible example, that reproduces this issue. I hope this helps. ---
**Author:** ![t.higashi](https://avatars.discourse-cdn.com/v4/letter/t/ea666f/32.png) [@t.higashi](https://forums.balena.io/u/t.higashi)\ **Post date:** [August 28, 2019, 9:43am UTC](https://forums.balena.io/t/after-updating-balena-os-bluetoothctl-can-not-be-used/18868/21 "2019-08-28T09:43:07Z")
Sorry, for delay. It was solved by setting the following. `DBUS_SYSTEM_BUS_ADDRESS=unix:path=/host/run/dbus/system_bus_socket` Thank you.