Re: [lxc-users] LXD containers always start

2016-10-19 Thread Christian Tardif
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 containers always start On Thu, O

Re: [lxc-users] LXD containers always start

2016-10-19 Thread Stéphane Graber
On Thu, Oct 20, 2016 at 03:09:01AM +, Christian Tardif wrote: > 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

[lxc-users] LXD containers always start

2016-10-19 Thread Christian Tardif
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

Re: [lxc-users] sudo dpkg-reconfigure -p medium lxd no longer works, what's the alternative

2016-10-19 Thread Stéphane Graber
On Wed, Oct 19, 2016 at 09:01:34PM -0500, David Favor wrote: > net12 # sudo dpkg-reconfigure -p medium lxd > Warning: Stopping lxd.service, but it can still be activated by: > lxd.socket > net12 # > > dpkg-reconfigure no longer allows reconfiguring lxd networking. > > Someone let me know altern

[lxc-users] sudo dpkg-reconfigure -p medium lxd no longer works, what's the alternative

2016-10-19 Thread David Favor
net12 # sudo dpkg-reconfigure -p medium lxd Warning: Stopping lxd.service, but it can still be activated by: lxd.socket net12 # dpkg-reconfigure no longer allows reconfiguring lxd networking. Someone let me know alternatives. Thanks. ___ lxc-users m

Re: [lxc-users] How can I “exec” a network namespace (ip netns) inside an lxc container

2016-10-19 Thread Yinon
Adding the steps taken to launch the container: lxc profile create devstack-profile lxc profile set devstack-profile linux.kernel_modules br_netfilter lxc profile device add devstack-profile eth0 nic nictype=bridged parent=br-lxd-mgmt lxc profile device add devstack-profile eth1 nic nictype=bridge

Re: [lxc-users] Looking for LXD-2.4.1 Static IP Setup Documentation

2016-10-19 Thread Matt Green
I've been effectively building a network interfaces file and pushing it to the container. I posted my script here: https://www.reddit.com/r/homelab/comments/50s7jz/lxd_automation_script/ I'm in the process of moving my build scripts to python, but that shell script worked. Matt On 19 October 201

Re: [lxc-users] Looking for LXD-2.4.1 Static IP Setup Documentation

2016-10-19 Thread Caleb Everett
https://github.com/lxc/lxd/issues/2050 On Wed, Oct 19, 2016 at 4:37 AM, Nicola Volpini wrote: > Hello > > ATM what I do is either use dnsmasq to provide DHCP or stop the > > container and push a preconfigured interfaces file... > > > > lxc file push interfaces.tmp CONTAINER/etc/network/interface

[lxc-users] How can I “exec” a network namespace (ip netns) inside an lxc container

2016-10-19 Thread Yinon
I installed an Ubuntu server 16.04. Inside I installed LXD and running an Ubuntu 16.04 container.Initially, I had this problem when trying to "ip netns add": mount –make-shared /var/run/netns failed: Permission denied And I did this to work around it: lxc config set container security.nesting tru

Re: [lxc-users] Looking for LXD-2.4.1 Static IP Setup Documentation

2016-10-19 Thread Nicola Volpini
Hello > ATM what I do is either use dnsmasq to provide DHCP or stop the > container and push a preconfigured interfaces file... > > lxc file push interfaces.tmp CONTAINER/etc/network/interfaces Same approach we are using, but with Ansible as our "bootstrapper/configurer". I've been successfully ab

Re: [lxc-users] lxc 2.0: command get_cgroup failed for 'dom1': Permission denied

2016-10-19 Thread Harald Dunkel
On 10/18/2016 08:59 AM, Harald Dunkel wrote: > Hi folks, > > since lxc 2.0 my monitoring scripts return error messages about > running system containers, e.g.: > > % lxc-ls -P /data1/lxc --fancy jerry1 > lxc-ls: commands.c: lxc_cmd_get_cgroup_path: 468 command get_cgroup failed > for 'jerry1': P