On 11/19/20 03:06, Nikos Mavrogiannopoulos wrote:
On Wed, Nov 18, 2020 at 2:23 PM Alexander Bokovoy wrote:
On ke, 18 marras 2020, Nikos Mavrogiannopoulos wrote:
Hi,
I realized my fedora-based containers have an /etc/resolv.conf which
claims it is managed by resolved, and nsswitch.conf has "res
On to, 19 marras 2020, Nikos Mavrogiannopoulos wrote:
On Wed, Nov 18, 2020 at 2:23 PM Alexander Bokovoy wrote:
On ke, 18 marras 2020, Nikos Mavrogiannopoulos wrote:
>Hi,
> I realized my fedora-based containers have an /etc/resolv.conf which
>claims it is managed by resolved, and nsswitch.conf
On 11/19/20 03:06, Nikos Mavrogiannopoulos wrote:
On Wed, Nov 18, 2020 at 2:23 PM Alexander Bokovoy wrote:
On ke, 18 marras 2020, Nikos Mavrogiannopoulos wrote:
Hi,
I realized my fedora-based containers have an /etc/resolv.conf which
claims it is managed by resolved, and nsswitch.conf has "res
On Wed, Nov 18, 2020 at 2:23 PM Alexander Bokovoy wrote:
>
> On ke, 18 marras 2020, Nikos Mavrogiannopoulos wrote:
> >Hi,
> > I realized my fedora-based containers have an /etc/resolv.conf which
> >claims it is managed by resolved, and nsswitch.conf has "resolve" in
> >hosts. However, doing someth
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
systemc
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 by dbus-broker which is not active by def
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 even
On ke, 18 marras 2020, Nikos Mavrogiannopoulos wrote:
Hi,
I realized my fedora-based containers have an /etc/resolv.conf which
claims it is managed by resolved, and nsswitch.conf has "resolve" in
hosts. However, doing something like
# systemd-resolve --status
results to:
sd_bus_open_system: No
