> On Sep 9, 2019, at 12:16, Ansgar Burchardt wrote:
>
> Johannes Ernst writes:
>> I've been running the same systemd-nspawn container for some time, always
>> with the same options:
>>
>> systemd-nspawn -b -n -D dir -M name --bind /home -x
>>
>> It would always bring up the virtual
Johannes Ernst writes:
> I've been running the same systemd-nspawn container for some time, always
> with the same options:
>
> systemd-nspawn -b -n -D dir -M name --bind /home -x
>
> It would always bring up the virtual ethernet link immediately during
> boot of the container. But since a
I've been running the same systemd-nspawn container for some time, always with
the same options:
systemd-nspawn -b -n -D dir -M name --bind /home -x
It would always bring up the virtual ethernet link immediately during boot of
the container. But since a recent Arch (host) upgrade (I
