Re: systemd-networkd and networking service in vagrant boxes

To: debian-cloud@lists.debian.org
Subject: Re: systemd-networkd and networking service in vagrant boxes
From: Nicolas Quiniou-Briand <nqb+listes@azyx.fr>
Date: Mon, 10 Jun 2019 17:56:15 +0200
Message-id: <[🔎] 4a77c59e-8736-30dc-5aad-5f586edcdd9c@azyx.fr>
In-reply-to: <[🔎] 4764d18c-3018-ec3b-4106-4d43cc52f82c@libera.cc>
References: <[🔎] 4325acf5-3333-616f-c5d3-ef115f7c80d6@azyx.fr> <[🔎] 4764d18c-3018-ec3b-4106-4d43cc52f82c@libera.cc>

Hello Emmanuel,

On 2019-06-08 11:24 a.m., Emmanuel Kasper wrote:

This is unfortunately a known behaviour and also a bug.
VirtualBoxes images use ifupdown for network configuration, and Libvirt
images use systemd-networkd, due to a bug in vmdeboostrap.

Can you submit a bug report against the
cloud.debian.org package so we can properly track the issue ?


Thanks for your feedback. Yes I will do it.
--
Nicolas Quiniou-Briand
Jabber/XMPP : nqb@azyx.fr

Reply to:

References:
- systemd-networkd and networking service in vagrant boxes
  - From: Nicolas Quiniou-Briand <nqb@azyx.fr>
- Re: systemd-networkd and networking service in vagrant boxes
  - From: Emmanuel Kasper <emmanuel@libera.cc>

Prev by Date: Re: Releasing ppc64el cloud images with Buster
Next by Date: Bug#930367: cloud.debian.org: vagrant images: use systemd-networkd for virtualbox provider
Previous by thread: Re: systemd-networkd and networking service in vagrant boxes
Next by thread: Week 3: Debian Cloud Image Finder Weekly Report
Index(es):
- Date
- Thread