Re: multiple systemd-nspawn container name resolution

From	john doe <johndoe65534@mail.com>
Newsgroups	linux.debian.user
Subject	Re: multiple systemd-nspawn container name resolution
Date	2022-04-27 17:10 +0200
Message-ID	<EgRsK-bzqB-3@gated-at.bofh.it> (permalink)
References	<EgR9n-bz4t-11@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 4/27/2022 4:29 PM, basti wrote:
>
> Hello,
>
> i have setup multiple systemd-nspawn container with virtualEthernet=yes.
> Inside the container systemd-networkd and systemd-resolved are enabled.
> So far so good.
>
> Is there a way to disable the 169.254... networking for systemd?
> The problem is as followed:
>
> ip r
>
> 169.254.0.0/16 dev ve-test3 proto kernel scope link src 169.254.144.44
> 169.254.0.0/16 dev ve-test2 proto kernel scope link src 169.254.38.46
> 169.254.0.0/16 dev ve-test proto kernel scope link src 169.254.80.104
>
> So I only can ping test3.
> The same problem is with name resolution.
>

Not realy an answer, Systemd has also a mailing list! :)

--
John Doe

Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

multiple systemd-nspawn container name resolution basti <mailinglist@unix-solution.de> - 2022-04-27 16:50 +0200
  Re: multiple systemd-nspawn container name resolution john doe <johndoe65534@mail.com> - 2022-04-27 17:10 +0200

csiph-web