Re: [lxc-users] Something catastrophic just happened to LXC networking

Just want to point out that the restriction only occurs between the host and its containers. Outside of it, it can talk without problems. Christian Tardif -- Message d'origine -- De: "Christ

Re: [lxc-users] Something catastrophic just happened to LXC networking

pers/IPVLAN-The-beginning.pdf ---- Christian Tardif -- Message d'origine -- De: "Saint Michael" À: "LXC users mailing-list" Envoyé : 2016-11-07 10:57:43 Objet : [lxc-users] Som

[lxc-users] Wierd issue with high userID's

ark. And until we can solve this, LXD containers aren't that helpful to us, unfortunately. -------- Christian Tardif ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] LXD containers always start

OK perfect. Thanks! Christian Tardif -- Message d'origine -- De: "Stéphane Graber" À: "LXC users mailing-list" Envoyé : 2016-10-19 23:15:43 Objet : Re: [lxc-users] LXD contain

[lxc-users] LXD containers always start

I'm trying to restrict some containers from autobooting on every host restart. From the documentation, I tried two approaches: lxc config set boot.autostart false or lxc config set boot.autostart 0 None of these configs work. Containers always boot on restart. Checked in the container pr

[lxc-users] LXD: flag provided but not defined

y lxc exec command, but passed in the exec string to the container? Tried to surround with quotes, but it does not work. THanks, ---- Christian Tardif ___ lxc-users mailing list

[lxc-users] lxc-start failed to retrieve the index for eth1

ainer eth card name, I'm stucked. Has anyone experienced that this way? ---- Christian Tardif christian.tar...@servinfo.ca ___ lxc-users mailing list lxc-users@