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
systemctl enable --now dbus-broker
Without it even hostnamectl doesn't work, not just systemd-resolve.
What is the advantage of running systemd-resolved in a container?
Is that container doing mDNS or LLMNR or a split-dns VPN ?
The whole point of containers is isolation and minimal setups. Pulling
in Base OS components into each container seems a waste of resources?
It is part of systemd packaging and gets pulled in with that if you need
systemd -- like we need for FreeIPA CIs or FreeIPA container
deployments.
# rpm -qf /usr/lib/systemd/systemd-resolved
systemd-246.6-3.fc34.x86_64
--
/ Alexander Bokovoy
Sr. Principal Software Engineer
Security / Identity Management Engineering
Red Hat Limited, Finland
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
