On Sun, Mar 16, 2014 at 6:00 PM, arnaud gaboury
wrote:
>>
>> So we were not automatically upping the bridged interface from nspawn.
>> I pushed a change to git just now which does that. Thanks for testing.
>>
>> Tom
> Correct. The only way for me to bring it up at boot is to create a .
> network
>
> So we were not automatically upping the bridged interface from nspawn.
> I pushed a change to git just now which does that. Thanks for testing.
>
> Tom
Correct. The only way for me to bring it up at boot is to create a .
network profile with this inside
[Match]
Name = vb*
This hack works but
On Tue, Mar 11, 2014 at 6:42 PM, arnaud gaboury
wrote:
> Hi,
>
> I run a dahlia container on a hortensia machine. Both are Arch boxes,
> and container is managed with nspawn and networkd.
>
> When I boot the hortensia machine, part of the ip addr output is :
>
> gabx@hortensia ➤➤ ~ % ip addr
> ...
On Tue, Mar 11, 2014 at 6:42 PM, arnaud gaboury
wrote:
> I run a dahlia container on a hortensia machine. Both are Arch boxes,
> and container is managed with nspawn and networkd.
>
> When I boot the hortensia machine, part of the ip addr output is :
>
> gabx@hortensia ➤➤ ~ % ip addr
> ...
>
> I have tried many various configurations, but the vb-dahlia interface
> is always DOWN .
>
> What am I missing or misconfiguring ?
>
> Thank you for help
/etc/systemd/network/80-container-host0.network
[Match]
Name=vb-dahlia
[Network]
DHCP=no
DNS=192.168.1.254
[Address]
Address=192.168.1.94
Hi,
I run a dahlia container on a hortensia machine. Both are Arch boxes,
and container is managed with nspawn and networkd.
When I boot the hortensia machine, part of the ip addr output is :
gabx@hortensia ➤➤ ~ % ip addr
4: vb-dahlia: mtu 1500 qdisc noop master br0
state DOWN
