Hello all,
I am trying to create 3 containers and starting 3 containers. I wrote a c
program to create 3 containers and different c program to start 3
containers. As i wann to start all containers async, so forked and execl, so
that all are different process.
It started the first container,but
Are you daemonizing the containers (with lxc-start -d) ? That seems to
be the most useful for my when I spin up dozens of containers... I set
the lxc.console variable via a --define
lxc.console=/var/log/lxc/$container on when I run lxc-start. This
seems to work fine.
I'm not sure what is all in
On 9/5/2011 12:34 PM, Michael H. Warfield wrote:
On Mon, 2011-09-05 at 09:24 +0200, Papp Tamas wrote:
On 09/05/2011 08:38 AM, Jäkel, Guido wrote:
What is the right way to stop a container?
Dear Papp,
Like with the thread paradigm in computing langugages, the right
way is that the thread
On Tue, 2011-09-06 at 17:34 -0400, Brian K. White wrote:
On 9/5/2011 12:34 PM, Michael H. Warfield wrote:
On Mon, 2011-09-05 at 09:24 +0200, Papp Tamas wrote:
On 09/05/2011 08:38 AM, Jäkel, Guido wrote:
What is the right way to stop a container?
Dear Papp,
Like with the thread
Hi,
I have been facing problems getting lxc (more specifically, lxc-attach) to
work on Linux v3.1.0-rc4. When I run lxc-attach, I get the following error:
$ lxc-attach -n foo -- /bin/bash
lxc-attach: No such file or directory - failed to open '/proc/821/ns/pid'
lxc-attach: failed to enter the
