What you want to achieve? In my case the reason for using a bridge was that
I had some static IPv4 addresses and an IPv6 subnet attached to eth0.
In this case I created a profiile called webhost and added a nic device
like this:
lxc profile device add webhost eth1 nic nictype=bridged parent=br0
I assigned this profile to each "webhost" container.
e.g lxc profile assign box1 default,webhost
For each "webhost" container I created a file
/etc/network/interfaces.d/49-eth1-static.cfg with a manually created static
ip configuration for eth1 in the container.
This finally works for me, but your case may be totally different. I've
learned that in some scenarios it's important to learn how things work.
2017-06-29 15:23 GMT+02:00 Tomasz Chmielewski :
> I've set this bridge in /etc/network/interfaces on the host:
>
> # lxc network show br-testing
> config: {}
> description: ""
> name: br-testing
> type: bridge
> used_by:
> - /1.0/containers/TDv2-testing-307c906842-2017-06-29-11-55-34
> - /1.0/containers/TDv2-testing-bc29e3f587-2017-06-29-11-47-25
> - /1.0/containers/TDv2-testing-bc29e3f587-2017-06-29-11-49-17
> - /1.0/containers/TDv2-z-testing-a19ea62218-2017-06-29-10-31-48
> managed: false
>
>
> Because of this, it's unmanaged, and I'm not able to configure it via "lxc
> network edit":
>
> # lxc network edit br-testing
> error: Only managed networks can be modified.
>
>
> How do I best get this unmanaged network to be managed?
>
> This one unfortunately doesn't work - so I guess it will be some sort of
> removing the bridge from the config, then adding it with lxc:
>
> # lxc network set br-testing managed=true
> error: Only managed networks can be modified.
>
> But perhaps there is some "recommended" way?
>
>
> --
> Tomasz Chmielewski
> https://lxadm.com
> ___
> 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
