I am trying to get up and running with the dbus balena block but facing some issues
We have a dbus config file that needs to be placed at
/etc/dbus-1/system-d - and currently that is done using a custom device type Nebra-HNT
With the new dbus block and due to wanting to add other hardware support (ideally without needing custom device types for each) we wanted to get the dbus balenaBlock running.
Working on a customised container to bring in the custom config file at https://github.com/NebraLtd/hm-dbus
The issues I’m having are as follows:
Firstly, when running with
DBUS_SYSTEM_BUS_ADDRESS=tcp:host=dbus-system,port=55884 I get an error saying “no address associated with hostname dbus-system:55884”
However when running using UNIX domain sockets, I get the issue “/var/run/dbus/pid already exists”. Deleting this file gets the dbus-system setup working, however the other containers still aren’t able to connect to it and pick up the custom dbus config file, but it’s not ideal to have to delete this every time. Maybe the removal of this file from the persistent storage can be incorporated into the entry.sh script?
Additionally using this implementation breaks functionality of bluez - I get error messages saying
The name org.bluez was not provided by any .service files. Adding in the bluetooth.conf file directly to this container does not work either… It then shows a message
unknown group "Bluetooth" in message bus configuration file
Do you have any tips or examples of the dbus block in an actual project?
Essentially all we want to do is inject this one custom dbus config file into the host OS but leave all other dbus setup the same.