D-Bus daemon don't work after ostree deployments.

[Yun Levi]

Hello, all.

I'm trying to install my custom package and mange via ostree.
For this, I try to create some kernel modules and make a branch like below

    mkdir -p /usr/lib/modules/5.15.18-200.fc35.x86_64/kernel/fs/
    cp mymod.ko /usr/lib/modules/5.15.18-200.fc35.x86_64/kernel/fs/
    
    ostree commit --base={comomit hash via rpm-ostree status -v} --branch=test/pkg/mymod
.
    // Get new commit hash
    ostree admin deploy --staged --kargs=systemd.debug-shell {new commit hash}
   
Command is success and kernel booting has no problem.
But while systemd starting D-Bus service, It prints below errors.

2026 Mar 03 01:16:15 localhost systemd[1]: Started D-Bus System Message Bus.
2027 Mar 03 01:16:15 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker
comm="systemd" exe="/usr/lib/systemd/     systemd" hostname=? addr=?
terminal=? res=success'
2028 Mar 03 01:16:15 localhost dbus-broker-launch[879]: ERROR launcher_run_child @
../src/launch/launcher.c +325: Permission denied
2029 Mar 03 01:16:15 localhost dbus-broker-launch[867]: ERROR service_add @
../src/launch/service.c +921: Transport endpoint is not connected
2030 Mar 03 01:16:15 localhost dbus-broker-launch[867]:       launcher_add_services @
../src/launch/launcher.c +804
2031 Mar 03 01:16:15 localhost dbus-broker-launch[867]:       launcher_run @
../src/launch/launcher.c +1409
2032 Mar 03 01:16:15 localhost dbus-broker-launch[867]:       run @ ../src/launch/main.c
+152
2033 Mar 03 01:16:15 localhost dbus-broker-launch[867]:       main @ ../src/launch/main.c
+178
2034 Mar 03 01:16:15 localhost dbus-broker-launch[867]: Exiting due to fatal error: -107
2035 Mar 03 01:16:15 localhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker
comm="systemd" exe="/usr/lib/systemd/s     ystemd" hostname=? addr=?
terminal=? res=failed'
2036 Mar 03 01:16:15 localhost systemd[1]: dbus-broker.service: Main process exited,
code=exited, status=1/FAILURE
2037 Mar 03 01:16:15 localhost systemd[1]: dbus-broker.service: Failed with result
'exit-code'.


I don't know why
    ../src/launch/launcher.c +325: Permission denied
happens, because /etc/machine-id has the same id to base image and permission has 0444
which means there should be no error on open.
(That code happen in sd_id128_get_machine function).

Am I missing somethings?

Thx.

[Colin Walters]

On Thu, Mar 3, 2022, at 1:06 AM, Yun Levi wrote:
>  Hello, all.
>
>  I'm trying to install my custom package and mange via ostree.
>  For this, I try to create some kernel modules and make a branch like below
>
>      mkdir -p /usr/lib/modules/5.15.18-200.fc35.x86_64/kernel/fs/
>      cp mymod.ko /usr/lib/modules/5.15.18-200.fc35.x86_64/kernel/fs/
>     
>      ostree commit --base={comomit hash via rpm-ostree status -v} 
>  --branch=test/pkg/mymod . 
Hi, what you're trying to do basically is something we're trying to address with
https://github.com/coreos/enhancements/blob/main/os/coreos-layering.md

The reason for the failure is you're committing a whole lot of data that shouldn't
be there, potentially even traversing into `/var`.  

People have asked a lot for us to make it easier on the ostree side to do exactly what
you're trying here, but there's a lot of subtleties.  The core problem is this
"commit from current commit" will end up creating hysteresis (
https://blog.verbum.org/2020/08/22/immutable-%E2%86%92-reprovisionable-an... )
- the state of the new system depends on the current one.

But what you really want is to be able to re-apply your changes on top of a new base, and
that's where we're going with the ostree native container flow - as a bonus the
result will be a standard container image one can push around, verify in CI etc.

[Yun Levi]

Thanks for answer!

I think i should use rpm package rather than layering!