[lxc-users] LXD 3.0 macvlan networking

Has something changed re networking with LXD 3.0 such that when using a macvlan that the host CAN ping a container? According to what I previously understood, and supported by this comment.. https://github.com/lxc/lxd/issues/3871#issuecomment-333124249 and the main reason I hadn't bothered even

Re: [lxc-users] Migration from LXD 2.x packages to LXD 3.0 snap

How exactly did you upgrade from 2.x deb to 3.0 snap? I've made a test "upgrade" on one server, but it didn't really result in an upgrade: - the old deb install was left with its containers and settings - the new snap version was installed in a different place, and was managing its own

Re: [lxc-users] Migration from LXD 2.x packages to LXD 3.0 snap

Thomas, I don't know if you have been able to answer your own question or not, but moving from 2.x on my workstation to 3.x did not interrupt the containers I had running on my local machine. It does not mean that if you have a specific filesystem back end (btrfs, zfs) that there isn't something

Re: [lxc-users] Macvlan explained

On Fri, May 4, 2018 at 10:34 AM, Michel Jansens wrote: > Hi, > > I just stumbled on this site and thought it would be nice to share: > > https://hicu.be/bridge-vs-macvlan > > It nicely explains how Macvlan work and how it compares with normal bridges. > In the case of

Re: [lxc-users] Macvlan explained

Dear Michel, Thank you! That's I was looking for long. From a quick look, IMHO the short paragraph about the Linux bridge miss the fact, that this "device" -- in addition to attach other NICs to it -- has a "build-in" pseudo-NIC to attach the hosts "IP Stack" here. Like the additional MACVLAN

[lxc-users] Macvlan explained

Hi, I just stumbled on this site and thought it would be nice to share: https://hicu.be/bridge-vs-macvlan It nicely explains how Macvlan work and how it compares with normal bridges. In the case of LXD, I suppose the macvlan bridge mode is used? It also mentions that although VMs cannot