On 6 April 2011 23:01, Daniel Lezcano wrote:
> On 04/03/2011 11:14 AM, Nigel McNie wrote:
>
>> Hi List,
>>
>>
>
>
> Nigel,
>
> Thanks a lot, that's a great work and it is exactly what I was hoping
> someone will do.
> I will be happy to take upstream these new commands.
>
> A mindless remark, I
Signed-off-by: Cedric Le Goater
---
doc/lxc-execute.sgml.in | 16
1 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/doc/lxc-execute.sgml.in b/doc/lxc-execute.sgml.in
index 9771318..77d132a 100644
--- a/doc/lxc-execute.sgml.in
+++ b/doc/lxc-execute.sgml.in
@@ -51,6
On Wednesday 06 April 2011 16:08:18 Rob Landley wrote:
> On 04/06/2011 05:43 AM, Daniel Lezcano wrote:
> > On 03/22/2011 10:20 AM, Nathan McSween wrote:
> >> Can I get a quick rundown of what is implemented w.r.t UID/GID
> >> containerization, is it safe yet to give containerized root to an
> >> e
On 04/06/2011 05:43 AM, Daniel Lezcano wrote:
> On 03/22/2011 10:20 AM, Nathan McSween wrote:
>> Can I get a quick rundown of what is implemented w.r.t UID/GID
>> containerization, is it safe yet to give containerized root to an
>> everyday user without huge security issues?
>
> Nope, it is not s
On 04/06/2011 02:26 PM, Jean-Philippe Menil wrote:
[ ... ]
> Is there anything to monitoring to be aware of when the network
> namespace is completly released?
> It's recurrent with a container running squid inside.
As you are using a non-random name for the veth peer network device
(cache2-cro
Le 06/04/2011 13:31, Daniel Lezcano a écrit :
> On 04/02/2011 11:18 PM, Jean-Philippe Menil wrote:
>> Hi,
>>
>> i experienced some strange problems when restarting a container.
>> Sometimes, it seems that the veth is not fully released on stop, then
>> the container failed to restart with the follo
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "lxc".
The branch, lxc-0.7.4.X has been updated
via 434d05fc6a8f38c29606780fab9df4fa3706fc25 (commit)
via 326afe510cccb9406f0
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "lxc".
The branch, master has been updated
via 25df6b78d2d013ee12e63ca80db3e572d89dcd6c (commit)
via 63e0f402aa028c02d15fc5fa
On 04/05/2011 09:23 PM, Cyril Brulebois wrote:
> Hi LXC folks,
>
> from my bug report against udev, so that it doesn't try to start when
> running in a non-root container:
>
> Marco d'Itri (05/04/2011):
>> On Apr 05, Cyril Brulebois wrote:
>>
>>> from a quick glance, it looks like running udev in
On 04/02/2011 11:18 PM, Jean-Philippe Menil wrote:
> Hi,
>
> i experienced some strange problems when restarting a container.
> Sometimes, it seems that the veth is not fully released on stop, then
> the container failed to restart with the following log:
> (in this case, the container have the sam
On 04/03/2011 11:14 AM, Nigel McNie wrote:
> Hi List,
>
> I saw there was a call for a nice frontend over the lxc commands, and I
> needed one, so Martyn Smith and I have come up with lxc-simple [0].
>
> Quoting the docs:
> "lxc-simple wraps around the low-level commands for controlling linux
> con
On 03/22/2011 10:20 AM, Nathan McSween wrote:
> Can I get a quick rundown of what is implemented w.r.t UID/GID
> containerization, is it safe yet to give containerized root to an
> everyday user without huge security issues?
Nope, it is not secure at all for a root user inside the container.
---
12 matches
Mail list logo
