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 <container> 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 back "The device doesn't exist". However this did list eth0 as a device: lxc config device list c1 eth0: nic eth1: nic thanks, Spike On Tue, Mar 7, 2017 at 8:11 AM Fajar A. Nugraha <l...@fajar.net> wrote: > On Tue, Mar 7, 2017 at 10:32 PM, Spike <sp...@drba.org> 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 docs suggesting that it can be done, but only for privileged > containers. Is that the case? Is it not possible at all for unprivileged > ones? > > > Short version: use lxd, set 'host_name' on the container interface config. > > You could probably do the same for root-owned, unpriv plain-lxc containers > (haven't test this though). > > -- > Fajar > _______________________________________________ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users
_______________________________________________ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users