[lxc-users] Containers losing IP/Network
Hello folks, I have some containers running ubuntu 14.01, but some times when I try to lxc-start a container, or create more containers, the network starts to behave strangely, some time a random container loses it's IP/network, some times all of them loses IP/network. This is a picture from my lxc-ls -f, as you can see I have containers RUNNING with no IP http://i.imgur.com/LIKXTe9.png This is the command that I use to create containers: lxc-create -n alabrunet -t ubuntu -B zfs And this is some extra config that I put on each container's config file # Hardware limitations lxc.cgroup.memory.limit_in_bytes = 10 lxc.cgroup.memory.soft_limit_in_bytes = 8 lxc.cgroup.cpu.shares = 100 lxc.cgroup.cpuset.cpus = 1 lxc.cgroup.blkio.weight = 500 The only thing that changes between configs is the lxc.cgroup.cpuset.cpus, I pick a core between 0 and 3. -- Alan Hoffmeister https://twitter.com/alan_hoff https://github.com/alanhoff https://keybase.io/alanhoff ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] Containers losing IP/Network
Where can I possibly locate a log file from the LXC's network manager? -- Alan Hoffmeister https://twitter.com/alan_hoff https://github.com/alanhoff https://keybase.io/alanhoff 2015-02-05 14:19 GMT-02:00 Joris Michaux : > Hello, > > Same problem here. Have to service networking restart into the container > to get it working. > > Regards, > Joris > > On 05/02/2015 17:12, Alan Hoffmeister wrote: >> Hello folks, >> >> I have some containers running ubuntu 14.01, but some times when I try >> to lxc-start a container, or create more containers, the network >> starts to behave strangely, some time a random container loses it's >> IP/network, some times all of them loses IP/network. >> >> This is a picture from my lxc-ls -f, as you can see I have containers >> RUNNING with no IP >> http://i.imgur.com/LIKXTe9.png >> >> This is the command that I use to create containers: >> lxc-create -n alabrunet -t ubuntu -B zfs >> >> And this is some extra config that I put on each container's config file >> # Hardware limitations >> lxc.cgroup.memory.limit_in_bytes = 10 >> lxc.cgroup.memory.soft_limit_in_bytes = 8 >> lxc.cgroup.cpu.shares = 100 >> lxc.cgroup.cpuset.cpus = 1 >> lxc.cgroup.blkio.weight = 500 >> >> The only thing that changes between configs is the >> lxc.cgroup.cpuset.cpus, I pick a core between 0 and 3. >> >> -- >> Alan Hoffmeister >> https://twitter.com/alan_hoff >> https://github.com/alanhoff >> https://keybase.io/alanhoff >> ___ >> lxc-users mailing list >> lxc-users@lists.linuxcontainers.org >> http://lists.linuxcontainers.org/listinfo/lxc-users >> > > > -- > *Joris MICHAUX* > Ingénieur systèmes et réseaux > *Skype:* h4mm3r.toxyc > > 425, rue Jean Rostand > 31670 Labège, France > *Tel:* +33 (0)5 82 08 07 31 > www.france-pari.fr - www.sportnco.com > > *Social:* > [facebook] > https://www.facebook.com/pages/France-Pari/ > [twitter] > https://twitter.com/FrancePari > [linkedin] > http://www.linkedin.com/company/france-pari > [scoop.it] > http://www.scoop.it/t/paris-sportifs-1 > ___ > 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
[lxc-users] Limit in/oubount network bandwidth
Hello folks, Is there a way to limit inbout/outbound netwoork bandwidth? Any tutorials? -- Alan Hoffmeister https://twitter.com/alan_hoff https://github.com/alanhoff https://keybase.io/alanhoff ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] Limit in/oubount network bandwidth
Anything more higher level? I'm new to TC and it would take a considerable amount of time to study it. -- Alan Hoffmeister https://twitter.com/alan_hoff https://github.com/alanhoff https://keybase.io/alanhoff 2015-02-09 9:15 GMT-02:00 Andy Billington : > does tc work (as it did with OpenVZ) ? > https://openvz.org/Traffic_shaping_with_tc > > On 9 February 2015 at 11:11, Alan Hoffmeister > wrote: >> >> Hello folks, >> >> Is there a way to limit inbout/outbound netwoork bandwidth? Any tutorials? >> >> -- >> Alan Hoffmeister >> https://twitter.com/alan_hoff >> https://github.com/alanhoff >> https://keybase.io/alanhoff >> ___ >> 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 ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
[lxc-users] LXD mock API
Hello folks, Is there a way to mock LDX rest API? I need it to write tests to a client. ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
[lxc-users] Limit open files per container
Hello there, I'm having some thoubles with max open files, some times a container eat all available descriptors lefting none to others, is there a simple way to avoid this? Thx! -- Alan Hoffmeister https://twitter.com/alan_hoff https://github.com/alanhoff https://keybase.io/alanhoff ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
[lxc-users] Error connecting to cgroup manager
Hello folks, I'm getting this messages when trying to autostart a vanilla ubuntu 14.04 guest on an ubntu 14.04 host, I'm using LXC 1.1.2 lxc-start 1433600022.910 ERRORlxc_cgmanager - cgmanager.c:cgm_destroy:571 - Error connecting to cgroup manager lxc-start 1433600096.266 ERRORlxc_cgmanager - cgmanager.c:cgm_bind_dir:1339 - /usr/lib/x86_64-linux-gnu/lxc/sys/fs/cgroup does not exist lxc-start 1433600096.286 ERRORlxc_conf - conf.c:lxc_mount_auto_mounts:846 - No such file or directory - error mounting /sys/fs/cgroup lxc-start 1433600096.286 ERRORlxc_conf - conf.c:lxc_setup:3847 - failed to setup the automatic mounts for 'test' lxc-start 1433600096.286 ERRORlxc_start - start.c:do_start:699 - failed to setup the container lxc-start 1433600096.286 ERRORlxc_sync - sync.c:__sync_wait:51 - invalid sequence number 1. expected 2 lxc-start 1433600096.319 ERRORlxc_start - start.c:__lxc_start:1164 - failed to spawn 'test' lxc-start 1433600101.324 ERRORlxc_start_ui - lxc_start.c:main:344 - The container failed to start. lxc-start 1433600101.325 ERRORlxc_start_ui - lxc_start.c:main:346 - To get more details, run the container in foreground mode. lxc-start 1433600101.325 ERRORlxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options -- Alan Hoffmeister https://twitter.com/alan_hoff https://github.com/alanhoff https://keybase.io/alanhoff ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] Error connecting to cgroup manager
Nothing, same error. -- Alan Hoffmeister https://twitter.com/alan_hoff https://github.com/alanhoff https://keybase.io/alanhoff 2015-06-08 12:19 GMT-03:00 Serge Hallyn : > Quoting Alan Hoffmeister (alanhoffmeis...@gmail.com): > > Hello folks, I'm getting this messages when trying to autostart a vanilla > > ubuntu 14.04 guest on an ubntu 14.04 host, I'm using LXC 1.1.2 > > > > lxc-start 1433600022.910 ERRORlxc_cgmanager - > > cgmanager.c:cgm_destroy:571 - Error connecting to cgroup manager > > lxc-start 1433600096.266 ERRORlxc_cgmanager - > > cgmanager.c:cgm_bind_dir:1339 - > /usr/lib/x86_64-linux-gnu/lxc/sys/fs/cgroup > > does not exist > > Hm, this looks like a race. lxc.conf starts on runlevel [2345]. > cgmanager starts on starting dbus. If cgmanager is slow to start, > I'm not sure there is anything stopping runlevel 2 from being entered > before > cgmanager is up. > > Does it reliably solve your issue if you change the 'start on' line in > /etc/init/lxc.conf to > > start on runlevel [2345] and started cgmanager > > ? > > > lxc-start 1433600096.286 ERRORlxc_conf - > > conf.c:lxc_mount_auto_mounts:846 - No such file or directory - error > > mounting /sys/fs/cgroup > > lxc-start 1433600096.286 ERRORlxc_conf - > conf.c:lxc_setup:3847 - > > failed to setup the automatic mounts for 'test' > > lxc-start 1433600096.286 ERRORlxc_start - > start.c:do_start:699 - > > failed to setup the container > > lxc-start 1433600096.286 ERRORlxc_sync - > sync.c:__sync_wait:51 - > > invalid sequence number 1. expected 2 > > lxc-start 1433600096.319 ERRORlxc_start - > > start.c:__lxc_start:1164 - failed to spawn 'test' > > lxc-start 1433600101.324 ERRORlxc_start_ui - > lxc_start.c:main:344 > > - The container failed to start. > > lxc-start 1433600101.325 ERRORlxc_start_ui - > lxc_start.c:main:346 > > - To get more details, run the container in foreground mode. > > lxc-start 1433600101.325 ERRORlxc_start_ui - > lxc_start.c:main:348 > > - Additional information can be obtained by setting the --logfile and > > --logpriority options > > > > -- > > Alan Hoffmeister > > https://twitter.com/alan_hoff > > https://github.com/alanhoff > > https://keybase.io/alanhoff > > > ___ > > 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 ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] Error connecting to cgroup manager
yes, exactly. -- Alan Hoffmeister https://twitter.com/alan_hoff https://github.com/alanhoff https://keybase.io/alanhoff 2015-06-15 12:20 GMT-03:00 Serge Hallyn : > to be clear, these containers start fine on the command line? > > Quoting Alan Hoffmeister (alanhoffmeis...@gmail.com): > > Nothing, same error. > > > > > > -- > > Alan Hoffmeister > > https://twitter.com/alan_hoff > > https://github.com/alanhoff > > https://keybase.io/alanhoff > > > > 2015-06-08 12:19 GMT-03:00 Serge Hallyn : > > > > > Quoting Alan Hoffmeister (alanhoffmeis...@gmail.com): > > > > Hello folks, I'm getting this messages when trying to autostart a > vanilla > > > > ubuntu 14.04 guest on an ubntu 14.04 host, I'm using LXC 1.1.2 > > > > > > > > lxc-start 1433600022.910 ERRORlxc_cgmanager - > > > > cgmanager.c:cgm_destroy:571 - Error connecting to cgroup manager > > > > lxc-start 1433600096.266 ERRORlxc_cgmanager - > > > > cgmanager.c:cgm_bind_dir:1339 - > > > /usr/lib/x86_64-linux-gnu/lxc/sys/fs/cgroup > > > > does not exist > > > > > > Hm, this looks like a race. lxc.conf starts on runlevel [2345]. > > > cgmanager starts on starting dbus. If cgmanager is slow to start, > > > I'm not sure there is anything stopping runlevel 2 from being entered > > > before > > > cgmanager is up. > > > > > > Does it reliably solve your issue if you change the 'start on' line in > > > /etc/init/lxc.conf to > > > > > > start on runlevel [2345] and started cgmanager > > > > > > ? > > > > > > > lxc-start 1433600096.286 ERRORlxc_conf - > > > > conf.c:lxc_mount_auto_mounts:846 - No such file or directory - error > > > > mounting /sys/fs/cgroup > > > > lxc-start 1433600096.286 ERRORlxc_conf - > > > conf.c:lxc_setup:3847 - > > > > failed to setup the automatic mounts for 'test' > > > > lxc-start 1433600096.286 ERRORlxc_start - > > > start.c:do_start:699 - > > > > failed to setup the container > > > > lxc-start 1433600096.286 ERRORlxc_sync - > > > sync.c:__sync_wait:51 - > > > > invalid sequence number 1. expected 2 > > > > lxc-start 1433600096.319 ERRORlxc_start - > > > > start.c:__lxc_start:1164 - failed to spawn 'test' > > > > lxc-start 1433600101.324 ERRORlxc_start_ui - > > > lxc_start.c:main:344 > > > > - The container failed to start. > > > > lxc-start 1433600101.325 ERRORlxc_start_ui - > > > lxc_start.c:main:346 > > > > - To get more details, run the container in foreground mode. > > > > lxc-start 1433600101.325 ERRORlxc_start_ui - > > > lxc_start.c:main:348 > > > > - Additional information can be obtained by setting the --logfile and > > > > --logpriority options > > > > > > > > -- > > > > Alan Hoffmeister > > > > https://twitter.com/alan_hoff > > > > https://github.com/alanhoff > > > > https://keybase.io/alanhoff > > > > > > > ___ > > > > 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 > > > ___ > > 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 > ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] Error connecting to cgroup manager
Yep, it worked. -- Alan Hoffmeister https://twitter.com/alan_hoff https://github.com/alanhoff https://keybase.io/alanhoff 2015-06-18 9:41 GMT-03:00 Alan Hoffmeister : > I was trying to avoid sleeps, it feels like a dirty solution, but I will > take a try. > > > -- > Alan Hoffmeister > https://twitter.com/alan_hoff > https://github.com/alanhoff > https://keybase.io/alanhoff > > 2015-06-17 23:39 GMT-03:00 Serge Hallyn : > >> Hm, so does adding a "sleep 1m" in /etc/init/lxc.conf right before >> the call to lxc-autostart help? >> >> Quoting Alan Hoffmeister (alanhoffmeis...@gmail.com): >> > yes, exactly. >> > >> > >> > -- >> > Alan Hoffmeister >> > https://twitter.com/alan_hoff >> > https://github.com/alanhoff >> > https://keybase.io/alanhoff >> > >> > 2015-06-15 12:20 GMT-03:00 Serge Hallyn : >> > >> > > to be clear, these containers start fine on the command line? >> > > >> > > Quoting Alan Hoffmeister (alanhoffmeis...@gmail.com): >> > > > Nothing, same error. >> > > > >> > > > >> > > > -- >> > > > Alan Hoffmeister >> > > > https://twitter.com/alan_hoff >> > > > https://github.com/alanhoff >> > > > https://keybase.io/alanhoff >> > > > >> > > > 2015-06-08 12:19 GMT-03:00 Serge Hallyn : >> > > > >> > > > > Quoting Alan Hoffmeister (alanhoffmeis...@gmail.com): >> > > > > > Hello folks, I'm getting this messages when trying to autostart >> a >> > > vanilla >> > > > > > ubuntu 14.04 guest on an ubntu 14.04 host, I'm using LXC 1.1.2 >> > > > > > >> > > > > > lxc-start 1433600022.910 ERRORlxc_cgmanager - >> > > > > > cgmanager.c:cgm_destroy:571 - Error connecting to cgroup manager >> > > > > > lxc-start 1433600096.266 ERRORlxc_cgmanager - >> > > > > > cgmanager.c:cgm_bind_dir:1339 - >> > > > > /usr/lib/x86_64-linux-gnu/lxc/sys/fs/cgroup >> > > > > > does not exist >> > > > > >> > > > > Hm, this looks like a race. lxc.conf starts on runlevel [2345]. >> > > > > cgmanager starts on starting dbus. If cgmanager is slow to start, >> > > > > I'm not sure there is anything stopping runlevel 2 from being >> entered >> > > > > before >> > > > > cgmanager is up. >> > > > > >> > > > > Does it reliably solve your issue if you change the 'start on' >> line in >> > > > > /etc/init/lxc.conf to >> > > > > >> > > > > start on runlevel [2345] and started cgmanager >> > > > > >> > > > > ? >> > > > > >> > > > > > lxc-start 1433600096.286 ERRORlxc_conf - >> > > > > > conf.c:lxc_mount_auto_mounts:846 - No such file or directory - >> error >> > > > > > mounting /sys/fs/cgroup >> > > > > > lxc-start 1433600096.286 ERRORlxc_conf - >> > > > > conf.c:lxc_setup:3847 - >> > > > > > failed to setup the automatic mounts for 'test' >> > > > > > lxc-start 1433600096.286 ERRORlxc_start - >> > > > > start.c:do_start:699 - >> > > > > > failed to setup the container >> > > > > > lxc-start 1433600096.286 ERRORlxc_sync - >> > > > > sync.c:__sync_wait:51 - >> > > > > > invalid sequence number 1. expected 2 >> > > > > > lxc-start 1433600096.319 ERRORlxc_start - >> > > > > > start.c:__lxc_start:1164 - failed to spawn 'test' >> > > > > > lxc-start 1433600101.324 ERRORlxc_start_ui - >> > > > > lxc_start.c:main:344 >> > > > > > - The container failed to start. >> > > > > > lxc-start 1433600101.325 ERRORlxc_start_ui - >> > > > > lxc_start.c:main:346 >> > > > > > - To get more details, run the container in foreground mode. >> > > > > > lxc-start 1433600101.325 ERRORlxc_start_ui - >> > > > > lxc_start.c:main:348 >> > > > > > - Additional information can be obtained by setting the >> --
Re: [lxc-users] Error connecting to cgroup manager
I was trying to avoid sleeps, it feels like a dirty solution, but I will take a try. -- Alan Hoffmeister https://twitter.com/alan_hoff https://github.com/alanhoff https://keybase.io/alanhoff 2015-06-17 23:39 GMT-03:00 Serge Hallyn : > Hm, so does adding a "sleep 1m" in /etc/init/lxc.conf right before > the call to lxc-autostart help? > > Quoting Alan Hoffmeister (alanhoffmeis...@gmail.com): > > yes, exactly. > > > > > > -- > > Alan Hoffmeister > > https://twitter.com/alan_hoff > > https://github.com/alanhoff > > https://keybase.io/alanhoff > > > > 2015-06-15 12:20 GMT-03:00 Serge Hallyn : > > > > > to be clear, these containers start fine on the command line? > > > > > > Quoting Alan Hoffmeister (alanhoffmeis...@gmail.com): > > > > Nothing, same error. > > > > > > > > > > > > -- > > > > Alan Hoffmeister > > > > https://twitter.com/alan_hoff > > > > https://github.com/alanhoff > > > > https://keybase.io/alanhoff > > > > > > > > 2015-06-08 12:19 GMT-03:00 Serge Hallyn : > > > > > > > > > Quoting Alan Hoffmeister (alanhoffmeis...@gmail.com): > > > > > > Hello folks, I'm getting this messages when trying to autostart a > > > vanilla > > > > > > ubuntu 14.04 guest on an ubntu 14.04 host, I'm using LXC 1.1.2 > > > > > > > > > > > > lxc-start 1433600022.910 ERRORlxc_cgmanager - > > > > > > cgmanager.c:cgm_destroy:571 - Error connecting to cgroup manager > > > > > > lxc-start 1433600096.266 ERRORlxc_cgmanager - > > > > > > cgmanager.c:cgm_bind_dir:1339 - > > > > > /usr/lib/x86_64-linux-gnu/lxc/sys/fs/cgroup > > > > > > does not exist > > > > > > > > > > Hm, this looks like a race. lxc.conf starts on runlevel [2345]. > > > > > cgmanager starts on starting dbus. If cgmanager is slow to start, > > > > > I'm not sure there is anything stopping runlevel 2 from being > entered > > > > > before > > > > > cgmanager is up. > > > > > > > > > > Does it reliably solve your issue if you change the 'start on' > line in > > > > > /etc/init/lxc.conf to > > > > > > > > > > start on runlevel [2345] and started cgmanager > > > > > > > > > > ? > > > > > > > > > > > lxc-start 1433600096.286 ERRORlxc_conf - > > > > > > conf.c:lxc_mount_auto_mounts:846 - No such file or directory - > error > > > > > > mounting /sys/fs/cgroup > > > > > > lxc-start 1433600096.286 ERRORlxc_conf - > > > > > conf.c:lxc_setup:3847 - > > > > > > failed to setup the automatic mounts for 'test' > > > > > > lxc-start 1433600096.286 ERRORlxc_start - > > > > > start.c:do_start:699 - > > > > > > failed to setup the container > > > > > > lxc-start 1433600096.286 ERRORlxc_sync - > > > > > sync.c:__sync_wait:51 - > > > > > > invalid sequence number 1. expected 2 > > > > > > lxc-start 1433600096.319 ERRORlxc_start - > > > > > > start.c:__lxc_start:1164 - failed to spawn 'test' > > > > > > lxc-start 1433600101.324 ERRORlxc_start_ui - > > > > > lxc_start.c:main:344 > > > > > > - The container failed to start. > > > > > > lxc-start 1433600101.325 ERRORlxc_start_ui - > > > > > lxc_start.c:main:346 > > > > > > - To get more details, run the container in foreground mode. > > > > > > lxc-start 1433600101.325 ERRORlxc_start_ui - > > > > > lxc_start.c:main:348 > > > > > > - Additional information can be obtained by setting the > --logfile and > > > > > > --logpriority options > > > > > > > > > > > > -- > > > > > > Alan Hoffmeister > > > > > > https://twitter.com/alan_hoff > > > > > > https://github.com/alanhoff > > > > > > https://keybase.io/alanhoff > > > > > > > > > > > ___ > > > > > > 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 > > > > > > > ___ > > > > 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 > > > > > > ___ > > 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 > ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] Error connecting to cgroup manager
That didn't worked :-( -- Alan Hoffmeister https://twitter.com/alan_hoff https://github.com/alanhoff https://keybase.io/alanhoff 2015-06-18 10:05 GMT-03:00 Serge Hallyn : > Heh, it wasn't a solution, but a debugging tool :) > > Let's try something perhaps a wee bit more elegant: in place of the > sleep, can you add something like > > while ! cgm ping 2>&1 > /dev/null; do sleep 1; done > > This is where upstart really failed (though it had plans) to > fix things - 'started cgmanager' means cgmanager has started, > but not that it is ready. Socket activation is a much better > model here. > > -serge > > Quoting Alan Hoffmeister (alanhoffmeis...@gmail.com): > > Yep, it worked. > > > > > > -- > > Alan Hoffmeister > > https://twitter.com/alan_hoff > > https://github.com/alanhoff > > https://keybase.io/alanhoff > > > > 2015-06-18 9:41 GMT-03:00 Alan Hoffmeister : > > > > > I was trying to avoid sleeps, it feels like a dirty solution, but I > will > > > take a try. > > > > > > > > > -- > > > Alan Hoffmeister > > > https://twitter.com/alan_hoff > > > https://github.com/alanhoff > > > https://keybase.io/alanhoff > > > > > > 2015-06-17 23:39 GMT-03:00 Serge Hallyn : > > > > > >> Hm, so does adding a "sleep 1m" in /etc/init/lxc.conf right before > > >> the call to lxc-autostart help? > > >> > > >> Quoting Alan Hoffmeister (alanhoffmeis...@gmail.com): > > >> > yes, exactly. > > >> > > > >> > > > >> > -- > > >> > Alan Hoffmeister > > >> > https://twitter.com/alan_hoff > > >> > https://github.com/alanhoff > > >> > https://keybase.io/alanhoff > > >> > > > >> > 2015-06-15 12:20 GMT-03:00 Serge Hallyn : > > >> > > > >> > > to be clear, these containers start fine on the command line? > > >> > > > > >> > > Quoting Alan Hoffmeister (alanhoffmeis...@gmail.com): > > >> > > > Nothing, same error. > > >> > > > > > >> > > > > > >> > > > -- > > >> > > > Alan Hoffmeister > > >> > > > https://twitter.com/alan_hoff > > >> > > > https://github.com/alanhoff > > >> > > > https://keybase.io/alanhoff > > >> > > > > > >> > > > 2015-06-08 12:19 GMT-03:00 Serge Hallyn < > serge.hal...@ubuntu.com>: > > >> > > > > > >> > > > > Quoting Alan Hoffmeister (alanhoffmeis...@gmail.com): > > >> > > > > > Hello folks, I'm getting this messages when trying to > autostart > > >> a > > >> > > vanilla > > >> > > > > > ubuntu 14.04 guest on an ubntu 14.04 host, I'm using LXC > 1.1.2 > > >> > > > > > > > >> > > > > > lxc-start 1433600022.910 ERRORlxc_cgmanager - > > >> > > > > > cgmanager.c:cgm_destroy:571 - Error connecting to cgroup > manager > > >> > > > > > lxc-start 1433600096.266 ERRORlxc_cgmanager - > > >> > > > > > cgmanager.c:cgm_bind_dir:1339 - > > >> > > > > /usr/lib/x86_64-linux-gnu/lxc/sys/fs/cgroup > > >> > > > > > does not exist > > >> > > > > > > >> > > > > Hm, this looks like a race. lxc.conf starts on runlevel > [2345]. > > >> > > > > cgmanager starts on starting dbus. If cgmanager is slow to > start, > > >> > > > > I'm not sure there is anything stopping runlevel 2 from being > > >> entered > > >> > > > > before > > >> > > > > cgmanager is up. > > >> > > > > > > >> > > > > Does it reliably solve your issue if you change the 'start on' > > >> line in > > >> > > > > /etc/init/lxc.conf to > > >> > > > > > > >> > > > > start on runlevel [2345] and started cgmanager > > >> > > > > > > >> > > > > ? > > >> > > > > > > >> > > > > > lxc-start 1433600096.286 ERRORlxc_conf - > > >> > > > > > conf.c:lxc_mo
Re: [lxc-users] Limit file descriptors
Thanks for the reply, I'm trying to allow root access to my containers so adjusting limits inside the rootfs isn't a good idea for me. -- Alan Hoffmeister https://twitter.com/alan_hoff https://github.com/alanhoff https://keybase.io/alanhoff 2016-03-18 3:08 GMT-03:00 Guido Jäkel : > Dear Alan, > > adjust the limits per Container in /etc/security/limits.conf , e.g. add > something like > > > * hardnofile 8192 > * softnofile 8000 > * hardnproc 1024 > * softnproc 1000 > > and maybe adjust the values at the host, too. > > > Greetings > > Guido > > > On 17.03.2016 00:40, Alan Hoffmeister wrote: > > Hello folks, > > > > I'm having some troubles where one container can drain the amount of file > > descriptors available in the host system. Does somebody knows how to > limit > > file descriptors per container? > > > > I'm running lxd v2.0.0.rc3 and lxc v2.0.0.rc10 > > > > Cheers > > > > -- > > Alan Hoffmeister > > https://twitter.com/alan_hoff > > https://github.com/alanhoff > > https://keybase.io/alanhoff > > > > > ___ > 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
[lxc-users] Limit file descriptors
Hello folks, I'm having some troubles where one container can drain the amount of file descriptors available in the host system. Does somebody knows how to limit file descriptors per container? I'm running lxd v2.0.0.rc3 and lxc v2.0.0.rc10 Cheers -- Alan Hoffmeister https://twitter.com/alan_hoff https://github.com/alanhoff https://keybase.io/alanhoff ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] OT: Btrfs or ZFS
It actually depends on what on how you want to store you data, here is a complete comparison between both: https://www.diva-portal.org/smash/get/diva2:822493/FULLTEXT01.pdf -- Alan Hoffmeister https://twitter.com/alan_hoff https://github.com/alanhoff https://keybase.io/alanhoff 2016-04-20 20:55 GMT-03:00 jjs - mainphrame : > I can tell you that when I tried btrfs in good faith, I was faced with > bugs that kept lxc from working correctly. Simply moving /var to ext4 > fixed everything. I haven't tried zfs yet, but it ought to be very > well supported for lxc. > > Jake > > > > On Wed, Apr 20, 2016 at 4:50 PM, 술욱 wrote: > > Hello list, > > > > What do you, users and devs, prefer, Btrfs or ZFS? > > > > My current setup is 2TB md raid1, Ext4. I was going to format Btrfs > > next weekend, but after reading the following link, I'm not so sure: > > > > > https://insights.ubuntu.com/2016/02/16/zfs-is-the-fs-for-containers-in-ubuntu-16-04/ > > > > > > Is there any preference in the LXC community on Btrfs vs ZFS? > > Are both FS well supported on LXC? > > Does any of these FS have LXC features the other one doesn't? > > > > I know this is a little off-topic but I don't know where else to ask > > for specific LXC features and/or preferences on FS. > > > > > > Many thanks in advance, > > Norberto > > ___ > > 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 > ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
