On Mon, 2011-10-17 at 23:04 +0300, Iliyan ilf Stoyanov wrote:
Hi again,
what about lxc-execute?
br,
--ilf
Hi,
lxc-execute is the lxc-start variant to run application containers.
Use lxc-attach if you need to issue a command in an already running
container.
Cheers.
On Mon, 2011-10-17
hi!
Is it possible to limit the maximum number of processes per container?
Thank you,
tamas
--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/06/2011 12:49 PM, Stéphane Graber wrote:
On 10/06/2011 12:51 AM, Daniel Baumann wrote:
On 10/06/2011 03:48 AM, Stéphane Graber wrote:
though a good part of that will probably have to happen in
Debian
which is why the bug should be
Quoting Ryan Campbell (ryan.campb...@gmail.com):
fedora 13
lxc 0.7.2-1.fc13
I've used lxc-setcap to allow non-root to run lxc-start. This seems to
work OK, until LXC attempts to launch init. Init fails with init:
Need to be root.
I would expect init to be launched using the 0 UID of
On 10/17/2011 5:01 PM, Papp Tamas wrote:
On 10/17/2011 10:54 PM, Derek Simkowiak wrote:
/I tried the python script, it just works fine./
Q1: How does the kill -INT init method affect running processes,
especially MySQL and other databases that may need to shutdown
gracefully to avoid data
On 10/18/2011 04:47 PM, Serge E. Hallyn wrote:
http://wiki.ubuntu.com/UserNamespace
I've got a few patches to send yet for tightening down some remaining
privilege leaks, then we should be ready to start relaxing things to make
them usable. This includes Eric's simple implementation of
On Tue, Oct 18, 2011 at 9:47 AM, Serge E. Hallyn
serge.hal...@canonical.com wrote:
Quoting Ryan Campbell (ryan.campb...@gmail.com):
fedora 13
lxc 0.7.2-1.fc13
I've used lxc-setcap to allow non-root to run lxc-start. This seems to
work OK, until LXC attempts to launch init. Init fails with
Quoting Papp Tamas (tom...@martos.bme.hu):
On 10/18/2011 04:47 PM, Serge E. Hallyn wrote:
http://wiki.ubuntu.com/UserNamespace
I've got a few patches to send yet for tightening down some remaining
privilege leaks, then we should be ready to start relaxing things to make
them usable.
On 10/18/2011 10:30 PM, Brian K. White wrote:
So after looking at the IEEE site about applying for an OUI, it seems to
me there needs to be some actual entity to do that appplication. Since I
am not a principle developer nor is my company more than an interested
user, I can't really just go
What is the best method for gracefully shutting down LXC containers
in a production environment?
By graceful, I mean that apps such as databases get a shutdown
signal, so they can save their data to disk, complete any pending
network ops, flush buffers, close filehandles, etc.
On Tue 2011-10-18 (15:22), Derek Simkowiak wrote:
What is the best method for gracefully shutting down LXC containers
in a production environment?
I use lxc -s container which itself executes a shutdown -h now via
cmdd, see: http://fex.rus.uni-stuttgart.de/lxc.html
lxc-attach -n CONTAINER
There is a behavior in the Linux kernel which can cause a bridge
device to change MAC address, thus causing a network blackout of several
seconds (while everybody ARPs the new MAC address flushes the old one).
This happens when bridging an enslaved interface, like we do with LXC.
On 10/18/2011 12:51 PM, Serge E. Hallyn wrote:
Quoting Papp Tamas (tom...@martos.bme.hu):
On 10/18/2011 04:47 PM, Serge E. Hallyn wrote:
http://wiki.ubuntu.com/UserNamespace
I've got a few patches to send yet for tightening down some remaining
privilege leaks, then we should be ready to
13 matches
Mail list logo
