We recently added tests to to ensure that interprocess communication (or [IPC](https://github.com/containers/toolbox/pull/1326 )), [networking](https://github.com/containers/toolbox/pull/1325 ) and [resource limits](https://github.com/containers/toolbox/pull/1328) work inside Toolbx containers. It will be good to add similar tests to ensure that [D-Bus](https://www.freedesktop.org/wiki/Software/dbus/) works inside Toolbx containers. We could test some simple method calls that can be expected to be present on all hosts. eg., on the session or user D-Bus instance: ``` $ gdbus call --session --dest org.freedesktop.DBus --object-path /org/freedesktop/DBus --method org.freedesktop.DBus.Peer.Ping () ``` ... and the system D-Bus instance: ``` $ gdbus call --system --dest org.freedesktop.systemd1 --object-path /org/freedesktop/systemd1 --method org.freedesktop.DBus.Properties.Get org.freedesktop.systemd1.Manager Version (<'253.5-1.fc38'>,) ``` Similarly other things that might be necessary to ensure to have *working D-Bus*. I expect the session or user instance to be just as functional inside Toolbx containers as it's on the host, but the system instance might be lacking in some aspects inside the container. It's time to find out! Instead of GLib's [gdbus(1)](https://man.archlinux.org/man/gdbus.1.en), one could also use systemd's [busctl(1)](https://www.freedesktop.org/software/systemd/man/busctl.html). It's a question of what's readily available inside the Toolbx containers and similar practical concerns.