<p dir="ltr"><br>
</p>
<p dir="ltr"></p>
<p dir="ltr">On Tue, Apr 28, 2015, 11:38 AM Lennart Poettering <<a href="mailto:mzerqung@0pointer.de">mzerqung@0pointer.de</a>> wrote:</p>
<blockquote><p dir="ltr">On Tue, 28.04.15 09:31, arnaud gaboury (<a href="mailto:arnaud.gaboury@gmail.com">arnaud.gaboury@gmail.com</a>) wrote:</p>
<p dir="ltr">> I started running Fedora server on a systemd-nspawn container.<br>
><br>
> I am wondering what is the best practice when an issue occurs:<br>
> - send to Fedora user ML<br>
> - send to systemd-devel ML<br>
> - send both with CC<br>
><br>
> I am afraid that when sending to only one list I will be told to ask<br>
> the other one, thus wasting time between the two lists. On the other<br>
> hand, CC to both lists can be viewed as spam.<br>
><br>
> From a user point of view, best would be to post to both lists as long<br>
> as the issue can come from systemd-nspawn functionality or Fedora.<br>
><br>
> use case: after install, boot, upgrade Fedora container, network is<br>
> down in container (when it used to work to install some new packages).<br>
><br>
> Thank you for advice about ML posting.</p>
<p dir="ltr">Cross-posting is not particularly popular, so I'd avoid it.</p>
</blockquote>
<p dir="ltr"></p>
<p dir="ltr">I know.</p>
<blockquote><p dir="ltr"></p>
<p dir="ltr">If it's nspawn related it's probably best to keep it on the systemd<br>
ML.</p>
<p dir="ltr">Consider using using systemd-networkd in the container and on the<br>
host. If so the network should just work between them.</p>
</blockquote>
<p dir="ltr"></p>
<p dir="ltr">I will as systemd- networkd already manage my network on the host. Btw, as fedora will act as a server, i will need a fix ip, get rid of ebtables and firewalld in container (kernel is built with apparmor and grsec) etc etc. Lot of work</p>
<blockquote><p dir="ltr"></p>
<p dir="ltr">Lennart</p>
<p dir="ltr">--<br>
Lennart Poettering, Red Hat<br>
</p>
</blockquote>
<p dir="ltr"><br>
</p>