If your host system i a ubuntu box, you can write an upstart script that will
automatically restart your container whenever it goes down. I guess init is the
equivalent of upstart in other distributions
On May 6, 2013, at 3:36 PM, David Parks wrote:
> Oh, that will do nicely. We'll just write
On Apr 25, 2013, at 12:54 PM, Elie Deloumeau wrote:
> Try 1024M
Thanks for your answer,
lxc allows the B, M and G notation. Tried to set 1024M but didn't solve my
problem. Definitely think this comes from the bad path:
/sys/fs/cgroup/memory//lxc, but I have no idea where too fix this---
Hello again,
I'm facing a strange issue (a bug maybe ?) on ubuntu 12.04. Creating a simple
container (lxc-create -t ubuntu -c cn0) and adding these lines in the config
file:
lxc.cgroup.memory.memsw.limit_in_bytes = 1G
lxc.cgroup.memory.limit_in_bytes = 512M
lxc.cgroup.cpu.shares = 512
results
Right, sorry to bother you with that, I launch my containers via an upstart
script, forgot the lxc-stop within the post-stop script… That's why I get so
many veth*
Thank you
On Apr 24, 2013, at 5:37 PM, Serge Hallyn wrote:
> the container netifs are created at lxc-start and destroyed at lxc-s
On Apr 24, 2013, at 3:53 PM, Serge Hallyn wrote:
> It would be far preferable to bind-mount /containers onto
> /var/lib/lxc and set the containers up there. If you're
> willing to do that and test it, then I'll happily look at
> the config files you are using and try to reproduce.
My setup is
Hello,
I create my containers a particular way:
- mount an existing container into the /containers/ folder
- manually change the config for the new container
- start the new container by specifying the path (-f option)
Then, to destroy it, I just stop it, unmount and remove everything. The proble
I'd like to be able to clone a lxc container over the network. For example, I
have a machine that contains lxc containers and on another machine, clone these
containers and use them. Any idea ?--
Precog is a next-generati
