[systemd-devel] Systemd-nspawn -- Unable to initialize virtual ethernet connection

[James Lott]

Thanks so much for debugging that!

Your recommended work around, of course, works perfectly for me until the 
release hits the Arch repos (although my gentoo machines will happily and 
impatiently pull in the git snapshot  ).

Do you know what the version number for the next systemd release will be? I 
want to make sure I keep my eyes peeled for it!

On Friday 19 September 2014 23:04:40 Tom Gundersen wrote:
> On Fri, Sep 19, 2014 at 6:37 PM, James Lott <james at lottspot.com> wrote:
> > I am trying to setup and play around with some of the private networking
> > features of systemd, and one of the big thinks I'm trying to get working
> > is
> > the virtual ethernet links. For some reason though, I am unable to start a
> > containder using a virtual ethernet link. My attempt is included below.
> 
> This is a bug. Thanks for the report!
> 
> I now pushed a fix:
> <http://cgit.freedesktop.org/systemd/systemd/commit/?id=c00524c9cc7fb498c724
> 4350e25823b8352f078c>.
> 
> The problem was that we were not correctly truncating the machine name
> (by default taken from the folder name) when using it to create a veth
> link. Until the fix lands in your distro, you can simply rename your
> container instance to a shorter name using the "--machine" switch to
> systemd-nspawn.
> 
> Cheers,
> 
> Tom