On Mon, 2011-12-12 at 08:43 +0100, Ulli Horlacher wrote:
> On Sun 2011-12-11 (19:48), Derek Simkowiak wrote:
>
> > The problem is not related to the setfd option. It is caused by
> > the bridge acquired a new MAC address. Libvirt already has a fix for
> > this, and there is a patch in th
2011/12/13 Zhu Yanhai :
> Hi,
>
> 2011/12/13 Derek Simkowiak :
>>> I'm trying to compose a system, where lxc containers behave like virtual
>>> hosts for a web server.
>>
>> It is possible to use shared, read-only mounts between the host and
>> containers. However, you will need to carefully c
Hi,
2011/12/13 Derek Simkowiak :
>> I'm trying to compose a system, where lxc containers behave like virtual
>> hosts for a web server.
>
> It is possible to use shared, read-only mounts between the host and
> containers. However, you will need to carefully consider your security
> requiremen
Hi,
(I'm sorry if this message is not properly attached to its original
thread; I found it on a mailing list archive while investigating a very
similar bug, and joined the mailing list afterwards!)
We are experiencing symptoms very similar to those described by Ulli
Horlacher:
- after a while
Hi,
I'm new in lxc and I have some doubts about it.
Is lxc platform dependent?
Could I use lxc in the MPC837x processor?
The support to checkpoint/resume commands will be work in this platform?
I'm need to build a High Availability system with MPC837x processor and
I'm planning to use the lxc
> /I'm trying to compose a system, where lxc containers behave like
virtual hosts for a web server./
It is possible to use shared, read-only mounts between the host and
containers. However, you will need to carefully consider your security
requirements and maintenance procedures.
If
Quoting Gordon Henderson (gor...@drogon.net):
> On Thu, 8 Dec 2011, Arie Skliarouk wrote:
>
> > When I tried to restart the vserver, it did not came up. Long story short,
> > I found that lxc-destroy did not destroy the cgroup of the same name as the
> > server. The cgroup remains visible in the /
On Thu, 8 Dec 2011, Arie Skliarouk wrote:
> When I tried to restart the vserver, it did not came up. Long story short,
> I found that lxc-destroy did not destroy the cgroup of the same name as the
> server. The cgroup remains visible in the /sys/fs/cgroup/cpu/master
> directory. The tasks file is
On Mon, 12 Dec 2011, István Király - LaKing wrote:
Hi folks.
I'm trying to compose a system, where lxc containers behave like virtual
hosts for a web server.
As next step I would like to minimize container size. My question is,
what the best, most elegant and fail proof technique for that?
Hi folks.
I'm trying to compose a system, where lxc containers behave like virtual hosts
for a web server.
As next step I would like to minimize container size. My question is, what the
best, most elegant and fail proof technique for that?
At this moment I'm thinking of a "master container" a
On Mon, 2011-12-12 at 11:54 +0530, nishant mungse wrote:
> Hi Geordy,
>
Hi Nishant,
I removed Cc: to containers@ as your troubles are about using the lxc
userspace tool: lxc-users@ is THE place for seeking help.
> This script gives the IP address of running system, but what I want is
> to get t
On 12/12/2011 04:48 AM, Derek Simkowiak wrote:
> When there are only one bridge on the system or the bridges are not
> connected together, this option is pointless and we can set the delay to
> '0'. That makes the port to be enabled instantaneously, hence the
> container can access the network imme
12 matches
Mail list logo
