[Error?] bolt.service in Aeon (Tumbleweed) distrobox

[Aqua1ung]

I created a Tumbleweed distrobox ("essentials") on my Aeon system, and installed bolt-utils in there, since Aeon does not come with boltctl:

distrobox-enter essentials -- sudo zypper install bolt-tools.

I then exported the boltctl binary, and attempted to start the bolt.service service (sudo systemctl enable bolt.service --now), and, while the service did start, the system complained that the bolt.service file is incomplete:

dad@localhost:~> sudo systemctl enable bolt --now
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.
 
Possible reasons for having these kinds of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/, .requires/, or .upholds/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.

Indeed I checked the corresponding file, and here below is what that service looks like. Like I said, while the service seems to be running, it does not do anything--in particular, boltctl list does not reflect any changes in the Thunderbolt configuration of the system. My guess is, again, that this is due to the incompleteness of the bolt.service file. Can anyone help me add the missing sections to the bolt.service?

📦[dad@essentials2 ~]$ cat /usr/lib/systemd/system/bolt.service
[Unit]
Description=Thunderbolt system service
After=polkit.service
Documentation=man:boltd(8)

[Service]
Type=dbus
BusName=org.freedesktop.bolt
ExecStart=/usr/libexec/boltd
#Environment="G_MESSAGES_DEBUG=all"
Restart=on-failure
NotifyAccess=main
WatchdogSec=3min

MemoryDenyWriteExecute=yes
PrivateTmp=yes
ProtectControlGroups=yes
ProtectHome=yes
ProtectKernelModules=yes
ProtectSystem=full
RestrictAddressFamilies=AF_NETLINK AF_UNIX
RestrictRealtime=yes
SystemCallFilter=~@mount
CapabilityBoundingSet=CAP_NET_ADMIN

#directory management
RuntimeDirectory=boltd
RuntimeDirectoryPreserve=yes
StateDirectory=boltd

[Aqua1ung]

Apparently bolt.service comes with Aeon natively, though I am not sure where they get it from. It may then be that Distrobox has nothing to do with this issue. If so, feel free to close this ticket.

[dottorblaster]

Howdy :-)

On my Aeon workstation bolt is installed by default, enabled and active. boltctl tho interacts with the daemon through dbus so you might want to install bolt-tools on your base system.

Another way of achieving this result could be specifying your host' dbus address when creating a dedicated distrobox:

distrobox create --additional-flags "--env DBUS_SYSTEM_BUS_ADDRESS=unix:path=/run/host/var/run/dbus/system_bus_socket"

This way you could let your distrobox connect to your host' dbus.

I have no experience with such a use case, so I can't be helpful.

https://unix.stackexchange.com/questions/778021/how-can-i-access-my-host-systems-system-dbus-bus-in-a-distrobox-container

I'll leave the issue open for a while if you need to ask further questions.

[Aqua1ung]

Another way of achieving this result could be specifying your host' dbus address when creating a dedicated distrobox:

distrobox create --additional-flags "--env DBUS_SYSTEM_BUS_ADDRESS=unix:path=/run/host/var/run/dbus/system_bus_socket"

This way you could let your distrobox connect to your host' dbus.

There is no /run/host/var/run/dbus/system_bus_socket folder (or file) on my machine (actually there is no /run/host folder to begin with), which, I am guessing, justifies the error below. Should I create one myself?

dad@localhost:~> boltctl list
boltctl: error: could not create client: Error connecting to D-Bus: Could not connect: No such file or directory