Volume mount /var/lib/bluetooth

Is it possible to volume mount /var/lib/bluetooth into the application container?

You should be able to use the Docker compose volumes field to do this. Check the volumes key resin docs and more info in the Docker compose docs. For example, you’d only have to add the following:

  - /var/lib/bluetooth

I know how to do that in docker but I do not have a docker-compose file in my repo for my resin.io application.

(please forgive the dumb questions as I have taken this over from another developer who has gone on holiday to NewZealand)

If there is no docker-compose file I assume that the resin system creates one?

Is this link relevant? https://docs.resin.io/learn/develop/multicontainer/

yes, the above link is relevant and explains how to write a small docker-compose file for your application that should be placed at the root directory of your project. If you take a look at this sample project for instance: https://github.com/resin-io-projects/multicontainer-getting-started
you’ll see that you can define a Dockerfile for each of your images, and a small docker-compose at the root dir to handle the containers.

Bind mounts are disallowed:


  • /var/lib/bluetooth

gives an error

[Error] Could not parse compose file

[Error] Bind mounts are not allowed

[Error] Not deploying release.

Here is the compose file:

version: ‘2.1’

networks: {}


resin-data: {}




context: .

privileged: true

restart: always

network_mode: host


  • ‘/var/lib/bluetooth’

  • ‘resin-data:/data’


io.resin.features.kernel-modules: ‘1’

io.resin.features.firmware: ‘1’

io.resin.features.dbus: ‘1’

io.resin.features.supervisor-api: ‘1’

io.resin.features.resin-api: ‘1’

io.resin.update.strategy: download-then-kill

io.resin.update.handover-timeout: ‘’

Please close this issue as it appears the problem was with the bluetooth target device and not resin image.

Thanx for your help - sorry about the noise

Thanks for letting us know, ticking this off our list now!