't operate.
Failed to connect to bus: Host is down
Is there a way to use systemd resolved in a container?
I figured this out yesterday -- at least in Rawhide, dbus-daemon is now
replaced by dbus-broker which is not active by default.
So you need
systemctl enable --now dbus-broker
Without it e
been booted with systemd as init system (PID 1). Can't operate.
>Failed to connect to bus: Host is down
>
>
>Is there a way to use systemd resolved in a container?
I figured this out yesterday -- at least in Rawhide, dbus-daemon is now
replaced by dbus-broker which is not active by defau
't operate.
Failed to connect to bus: Host is down
Is there a way to use systemd resolved in a container?
I figured this out yesterday -- at least in Rawhide, dbus-daemon is now
replaced by dbus-broker which is not active by default.
So you need
systemctl enable --now dbus-broker
Without it e
has not been booted with systemd as init system (PID 1). Can't
> >operate.
> >Failed to connect to bus: Host is down
> >
> >
> >Is there a way to use systemd resolved in a container?
>
> I figured this out yesterday -- at least in Rawhide, dbus-daemon is now
On ke, 18 marras 2020, Paul Wouters wrote:
On Wed, 18 Nov 2020, Alexander Bokovoy wrote:
Is there a way to use systemd resolved in a container?
I figured this out yesterday -- at least in Rawhide, dbus-daemon is now
replaced by dbus-broker which is not active by default.
So you need
On Wed, Nov 18, 2020 at 6:37 PM Paul Wouters wrote:
>
> On Wed, 18 Nov 2020, Alexander Bokovoy wrote:
>
> >> Is there a way to use systemd resolved in a container?
> >
> > I figured this out yesterday -- at least in Rawhide, dbus-daemon is now
> > replaced b
On Wed, 18 Nov 2020, Alexander Bokovoy wrote:
Is there a way to use systemd resolved in a container?
I figured this out yesterday -- at least in Rawhide, dbus-daemon is now
replaced by dbus-broker which is not active by default.
So you need
systemctl enable --now dbus-broker
Without it
system: No such file or directory
Trying to start dbus claims that systemd is not the init:
# systemctl start dbus
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
Is there a way to use systemd resolved in a container?
bus claims that systemd is not the init:
# systemctl start dbus
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
Is there a way to use systemd resolved in a container?
regards,
Nikos
__
