ah, thanks, I had seen that help output from trying illegal commands but
somehow I missed the obvious - reading is hard at times.
good tip on abbreviating the names, love the insights of people who have
done it before, experience ftw.
thanks,
Spike
On Tue, Mar 7, 2017 at 1:57 PM Fajar A.
thanks Fajar, that worked perfectly. That said, I'm still very new to
lxd/lxc and the only way I could get that done was to run:
lxc config edit
how would I have set the property for the device? I tried:
lxc config device set x1 eth0.host_name = veth_c1_eth0
but that didn't work and I got
On 07.03.2017 17:11, Fajar A. Nugraha wrote:
> On Tue, Mar 7, 2017 at 10:32 PM, Spike wrote:
>
>> Dear all,
>>
>> I'm using bridged mode for networking and would love to be able to tell
>> which veth is which on the host by using more meaningful names. This would
>> also very
On Tue, Mar 7, 2017 at 10:32 PM, Spike wrote:
> Dear all,
>
> I'm using bridged mode for networking and would love to be able to tell
> which veth is which on the host by using more meaningful names. This would
> also very useful for monitoring and debugging.
>
> I found some
Dear all,
I'm using bridged mode for networking and would love to be able to tell
which veth is which on the host by using more meaningful names. This would
also very useful for monitoring and debugging.
I found some docs suggesting that it can be done, but only for privileged
containers. Is