Bug 2391342

Summary: Running dbus-broker in rawhide container fails
Product: [Fedora] Fedora Container Images Reporter: Jan Pazdziora <adelton>
Component: baseAssignee: Clement Verna <clems.verna>
Status: NEW --- QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 45   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jan Pazdziora 2025-08-27 19:30:17 UTC
Description of problem:

In the https://github.com/freeipa/freeipa-container project we build Fedora-based FreeIPA server images in https://quay.io/repository/freeipa/freeipa-server?tab=tags. The FreeIPA containers are systemd-based and we depend on systemd and dbus working.

In latest registry.fedoraproject.org/fedora:rawhide with systemd installed, we observe that dbus-broker fails to start.

Version-Release number of selected component (if applicable):

REPOSITORY                         TAG         IMAGE ID      CREATED       SIZE
registry.fedoraproject.org/fedora  rawhide     ac69f932f370  2 days ago    184 MB

with systemd 258~rc3-2.fc44 installed.

How reproducible:

Deterministic.

Steps to Reproduce:
1. Have Dockerfile

FROM specify-image-with-from-parameter
RUN dnf install --setopt=install_weak_deps=False -y systemd
ENTRYPOINT [ "/usr/sbin/init" ]
STOPSIGNAL RTMIN+3

2. Build Fedora 42 and Fedora rawhide images with rootless podman:

   $ podman build --from registry.fedoraproject.org/fedora:42 -t localhost/fedora-init:42 .
   $ podman build --from registry.fedoraproject.org/fedora:rawhide -t localhost/fedora-init:rawhide .

3. Run Fedora 42 systemd container:

   $ podman run --rm -ti --name fedora-init-42 localhost/fedora-init:42

4. From another terminal check that dbus-broker service is running:

   $ podman exec -ti fedora-init-42 systemctl status dbus-broker
● dbus-broker.service - D-Bus System Message Bus
     Loaded: loaded (/usr/lib/systemd/system/dbus-broker.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Wed 2025-08-27 19:26:07 UTC; 6s ago
 Invocation: a11ab904f5544a9ca1f57daaf01f364d
TriggeredBy: ● dbus.socket
       Docs: man:dbus-broker-launch(1)
   Main PID: 35 (dbus-broker-lau)
      Tasks: 2 (limit: 307)
     Memory: 1.1M (peak: 2.1M)
        CPU: 9ms
     CGroup: /system.slice/dbus-broker.service
             ├─35 /usr/bin/dbus-broker-launch --scope system --audit
             └─37 dbus-broker --log 4 --controller 9 --machine-id dd4eb2cf674143ef88b5f6162aad6450 --max-bytes 536870912 --max-fds 4096 --max-matches 16384 --audit

Aug 27 19:26:07 2f01e1f9eac7 systemd[1]: Starting dbus-broker.service - D-Bus System Message Bus...
Aug 27 19:26:07 2f01e1f9eac7 systemd[1]: Started dbus-broker.service - D-Bus System Message Bus.
Aug 27 19:26:07 2f01e1f9eac7 dbus-broker-launch[35]: Ready

5. From that second terminal,

   $ podman rm -f fedora-init-42

6. Now repeat with the rawhide image:

   $ podman run --rm -ti --name fedora-init-rawhide localhost/fedora-init:rawhide

7. From another terminal, check

   $ podman exec -ti fedora-init-rawhide systemctl status dbus-broker

Actual results:

○ dbus-broker.service - D-Bus System Message Bus
     Loaded: loaded (/usr/lib/systemd/system/dbus-broker.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)
TriggeredBy: ● dbus.socket
       Docs: man:dbus-broker-launch(1)

Expected results:

dbus-broker.service active / running.

Additional info:

Attempt to start the service manually fails:

$ podman exec -ti fedora-init-rawhide systemctl start dbus-broker
$ podman exec -ti fedora-init-rawhide journalctl -l | grep dbus
Aug 27 19:27:54 dd57db4d12f4 systemd[1]: Listening on dbus.socket - D-Bus System Message Bus Socket.
Aug 27 19:29:02 dd57db4d12f4 systemd[1]: Starting dbus-broker.service - D-Bus System Message Bus...
Aug 27 19:29:02 dd57db4d12f4 systemd[1]: Started dbus-broker.service - D-Bus System Message Bus.
Aug 27 19:29:02 dd57db4d12f4 dbus-broker-launch[104]: ERROR util_audit_drop_permissions @ ../src/util/audit.c +81: Operation not permitted
Aug 27 19:29:02 dd57db4d12f4 dbus-broker-launch[102]: ERROR service_add @ ../src/launch/service.c +1011: Transport endpoint is not connected
Aug 27 19:29:02 dd57db4d12f4 dbus-broker-launch[102]:       launcher_add_services @ ../src/launch/launcher.c +823
Aug 27 19:29:02 dd57db4d12f4 dbus-broker-launch[102]:       launcher_run @ ../src/launch/launcher.c +1439
Aug 27 19:29:02 dd57db4d12f4 dbus-broker-launch[102]:       run @ ../src/launch/main.c +152
Aug 27 19:29:02 dd57db4d12f4 dbus-broker-launch[102]:       main @ ../src/launch/main.c +178
Aug 27 19:29:02 dd57db4d12f4 dbus-broker-launch[102]: Exiting due to fatal error: -107
$ podman exec -ti fedora-init-rawhide systemctl status dbus-broker
● dbus-broker.service - D-Bus System Message Bus
     Loaded: loaded (/usr/lib/systemd/system/dbus-broker.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: activating (start) since Wed 2025-08-27 19:29:48 UTC; 9ms ago
        Job: 410
 Invocation: 40e7f7bd649649cfaa72f9ce69c03b16
TriggeredBy: ● dbus.socket
       Docs: man:dbus-broker-launch(1)
   Main PID: 112 ((r-launch))
      Tasks: 1 (limit: 307)
     Memory: 1M (peak: 1M)
        CPU: 6ms
     CGroup: /system.slice/dbus-broker.service
             └─112 "(r-launch)"

Aug 27 19:29:48 dd57db4d12f4 systemd[1]: Starting dbus-broker.service - D-Bus System Message Bus...

Comment 1 Jan Pazdziora 2025-08-27 19:31:44 UTC
Also filed as Fedora systemd bug 2391343.

Comment 2 Jan Pazdziora 2025-10-30 05:50:55 UTC
The bug is now present on now-released Fedora 43 as well:

$ podman exec -ti fedora-init-43 systemctl status dbus-broker
○ dbus-broker.service - D-Bus System Message Bus
     Loaded: loaded (/usr/lib/systemd/system/dbus-broker.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)
TriggeredBy: ● dbus.socket
       Docs: man:dbus-broker-launch(1)

$ podman exec -ti fedora-init-43 systemctl start dbus-broker
$ podman exec -ti fedora-init-43 journalctl -l | grep dbus
Oct 30 05:49:18 2762b2e4ed99 systemd[1]: Listening on dbus.socket - D-Bus System Message Bus Socket.
Oct 30 05:49:46 2762b2e4ed99 systemd[1]: Starting dbus-broker.service - D-Bus System Message Bus...
Oct 30 05:49:46 2762b2e4ed99 systemd[1]: Started dbus-broker.service - D-Bus System Message Bus.
Oct 30 05:49:46 2762b2e4ed99 dbus-broker-launch[106]: ERROR util_audit_drop_permissions @ ../src/util/audit.c +81: Operation not permitted
Oct 30 05:49:46 2762b2e4ed99 dbus-broker-launch[104]: ERROR service_add @ ../src/launch/service.c +1011: Transport endpoint is not connected
Oct 30 05:49:46 2762b2e4ed99 dbus-broker-launch[104]:       launcher_add_services @ ../src/launch/launcher.c +823
Oct 30 05:49:46 2762b2e4ed99 dbus-broker-launch[104]:       launcher_run @ ../src/launch/launcher.c +1439
Oct 30 05:49:46 2762b2e4ed99 dbus-broker-launch[104]:       run @ ../src/launch/main.c +152
Oct 30 05:49:46 2762b2e4ed99 dbus-broker-launch[104]:       main @ ../src/launch/main.c +178
Oct 30 05:49:46 2762b2e4ed99 dbus-broker-launch[104]: Exiting due to fatal error: -107

Comment 3 Aoife Moloney 2026-08-17 13:59:21 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 45 development cycle.
Changing version to 45.