Bug#935948: can't start containers with different names but same prefix (xxxxxxxxxxx-1 and xxxxxxxxxxx-2)

[Michael Biebl]

Am 28.08.19 um 13:11 schrieb Trent W. Buck:

> If this is an unavoidable limitation due to Linux, please at least
> warn about it in the systemd-nspawn manpage.

I've forwarded this upstream to
https://github.com/systemd/systemd/issues/13417 where it was mentioned
that this topic had already come up and the fix was to document this
limitation. See

https://github.com/systemd/systemd/pull/11989/commits/6cc68362d529ca8b99fd6ca55b0fc7143e696aea

Have you seen this paragraph in systemd-nspawn?

I invite you to join the upstream bug tracker if you have further feedback.
Otherwise I'm going to close this bug report as this limitation is
actually documented:

>            Note that on Linux network interface names may have a length of 15 characters at maximum, while container names may have a length up to 64 characters. As this option derives the host-side interface name from the
>            container name the name is possibly truncated. Thus, care needs to be taken to ensure that interface names remain unique in this case, or even better container names are generally not chosen longer than 12
>            characters, to avoid the truncation. Alternatively, the --network-veth-extra= option may be used, which allows free configuration of the host-side interface name independently of the container name — but might
>            require a bit more additional configuration in case bridging in a fashion similar to --network-bridge= is desired.




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190828/c705522f/attachment.sig>