On Tue, Apr 28, 2015, 11:38 AM Lennart Poettering <mzerqung(a)0pointer.de>
wrote:
On Tue, 28.04.15 09:31, arnaud gaboury (arnaud.gaboury(a)gmail.com) wrote:
I started running Fedora server on a systemd-nspawn container.
I am wondering what is the best practice when an issue occurs:
- send to Fedora user ML
- send to systemd-devel ML
- send both with CC
I am afraid that when sending to only one list I will be told to ask
the other one, thus wasting time between the two lists. On the other
hand, CC to both lists can be viewed as spam.
From a user point of view, best would be to post to both lists as long
as the issue can come from systemd-nspawn functionality or Fedora.
use case: after install, boot, upgrade Fedora container, network is
down in container (when it used to work to install some new packages).
Thank you for advice about ML posting.
Cross-posting is not particularly popular, so I'd avoid it.
I know.
If it's nspawn related it's probably best to keep it on the systemd
ML.
Consider using using systemd-networkd in the container and on the
host. If so the network should just work between them.
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
Lennart
--
Lennart Poettering, Red Hat