Re: sibling DNS lookup of nspawn containers

[Petr Menšík <pemensik@xxxxxxxxxx>]

I am solving this by using libvir's network, which uses dnsmasq for
network resolution. That dnsmasq should be able to resolve names of
containers, because they were registered by DHCP requests. Because they
share dns cache at host, there is single place where they can register to.

Not directly related to systemd however.

On 6/18/21 5:26 AM, Johannes Ernst wrote:
> I’d like to be able to DNS lookup container b from within container a, if both were started with systemd-nspawn as siblings of each other, and shown as a and b in machinectl list.
>
> man nss-mymachines specifically notes it won’t do that.
>
> What’s the proper way of doing this?
>
> Thanks,
>
>
>
>
> Johannes.
>
> _______________________________________________
> systemd-devel mailing list
> systemd-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- 
Petr Menšík
Software Engineer
Red Hat, http://www.redhat.com/
email: pemensik@xxxxxxxxxx
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB

_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel