On Tue, May 20, 2014 at 08:07:39PM -0400, CDR wrote:
Dear Friends
I have 20+ containers with the same programs running. All of them are
cpu-intensive. But one of them is eating way more CPU than the
average. With top I have no idea which container owns that
program. Perhaps we need a new
On Wednesday 21 May 2014 01:07:39 CDR wrote:
Dear Friends
I have 20+ containers with the same programs running. All of them are
cpu-intensive. But one of them is eating way more CPU than the
average. With top I have no idea which container owns that
program. Perhaps we need a new lxc-top that
Hello all,
I'm trying to setup the following simple config :
* a lxc host (single network interface, single public IP1)
* a lxc container (single public IP2)
I would like to achieve the same as OpenVZ venet, where all containers
have dedicated IPs, but are sharing the MAC address of the
I did my lxc build with RPM
make rpm, and it did not built it.
What are the steps?
I am using Ubuntu Server
Philip
On Wed, May 21, 2014 at 7:50 AM, Steven Jan Springl
ste...@springl.co.uk wrote:
On Wednesday 21 May 2014 01:07:39 CDR wrote:
Dear Friends
I have 20+ containers with the same
Quoting CDR (vene...@gmail.com):
Wrong, that RPM was in Fedora, in Ubuntu I connected to a repository.
But lxc-top is not there.
How do I get that utility?
sudo apt-get install lua-lxc
Yeah that really should be more discoverable...
___
lxc-users
On Wed, May 21, 2014 at 9:19 PM, Marc MAURICE
marc.maur...@objectif-libre.com wrote:
I finally made it work with veth mode, and a bridge on the host, but it's
frustrating.
And I have to manually generate and allow all mac adresses (required by
my
server hoster).
I'd just comment on this
Thanks a lot.
I tried the config and it's *almost* working.
When pinging the output from the container : packets are going out with
the good MAC.
However, nothing in return.
From tcpdumps I figured out that my parent host is not responding to
arp for the container IP.
How do I tell my host
On Wed, May 21, 2014 at 10:34 PM, Marc MAURICE
marc.maur...@objectif-libre.com wrote:
Thanks a lot.
I tried the config and it's *almost* working.
When pinging the output from the container : packets are going out with the
good MAC.
However, nothing in return.
From tcpdumps I figured out
Dear Friends
I came upon a bug that needs to be addressed
Suppose you have a container with a network like this
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br20
lxc.network.hwaddr = 92:ea:2b:24:e0:27
lxc.network.ipv4 = 0.0.0.0/24
The container is UP, then you decide to
