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

Michael Biebl biebl at debian.org
Fri Aug 30 23:36:46 BST 2019


On Thu, 29 Aug 2019 11:21:37 +1000 "Trent W. Buck" <trentbuck at gmail.com>
wrote:
> Michael Biebl wrote:
> > 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 missed that somehow.
> Probably I was looking at a v241 manpage, which predates that commit.
> 
> I agree this ticket can be closed.  Sorry for wasting your time :-(
> 
> 

Let's keep this open for the time being. Apparently there is some
upstream work being done to make the naming scheme for veth interfaces a
bit smarter. Let's see where this goes.

-- 
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/20190831/b0f377b1/attachment.sig>


More information about the Pkg-systemd-maintainers mailing list