On Tue, 2012-01-03 at 11:10 +0100, Daniel Lezcano wrote:
> On 12/30/2011 12:14 PM, Ulli Horlacher wrote:
> > On Mon 2011-12-26 (18:25), Wai-kit Sze wrote:
> >
> >> What are the difference between application containers and system
> >> containers? Both of them can start a command directly.
> > An ap
On Wed, 2011-12-28 at 15:33 +0100, stefano zingaro wrote:
> Hi all, I would like to know if the actual linux kernel provides any
> implementations of Linux Containers for Checkpoint/Restart solutions.
> Any information will be very helpful. thanks
>
No. There have been some attempts (google is yo
Is there any other solution to this?
>
If your need is to defer the startup of some services, then it's an
upstart story... I don't know upstart but I guess it's possible to
configure it so that when you do lxc-start, a minimal set of services
will be started to provide networ
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 Thu, 2011-12-08 at 16:03 +0530, nishant mungse wrote:
> Hi,
>
> I want to manually invoke a networking setup to start the network
> service to get the IP address of container , But the problem is i
> don't want to start the container and want to use lxc-execute.
>
> When I tried these things h
1 0 Nov03 ?00:00:00 /usr/libexec/libvirt_lxc
> --name instance-0005 --console 15 --handshake 18 --background --veth veth1
> root 4922 4921 0 Nov03 ?00:00:00 \_ /sbin/init
> root 4927 4922 0 Nov03 ?00:00:00 \_ /sbin/agetty -8 38400
> /dev
> Nishant Mungse
> >
> > On Thu, Nov 3, 2011 at 3:41 PM, Greg Kurz
>
> > wrote:
> > On Thu, 2011-11-03
On Fri, 2011-11-04 at 11:04 +0530, nishant mungse wrote:
> On Thu, Nov 3, 2011 at 6:36 PM, Greg Kurz wrote:
> On Thu, 2011-11-03 at 17:07 +0530, nishant mungse wrote:
> > Hi Greg,
> >
> > I have one more doubt
On Thu, 2011-11-03 at 13:08 -0700, Dong-In David Kang wrote:
> Hello,
>
> I'm trying to use lxc-attach.
> The kernel I'm running is 2.6.38.8.
> I'm using lxc-0.7.5.
> When I run lxc-attach it tries to open /proc//ns/...,
> but I cannot find it.
> Did I configure the Linux kernel in a wrong way?
>
ote:
> Hi Greg,
>
> Thanks 4 reply. It is working now. Thanks
>
> Regards,
> Nishant Mungse
>
> On Thu, Nov 3, 2011 at 3:41 PM, Greg Kurz
> wrote:
> On Thu, 2011-11-03 at 11:25 +0530, nishant mu
On Thu, 2011-11-03 at 11:25 +0530, nishant mungse wrote:
> Hi,
>
> I am using lxc-execute command and in place of command to execute i am
> using bin/smbtorture //nishant/ubuntu -Uubuntu_user%passwd raw.write
> test.
>
> command::
> lxc-execute -n ubuntu_user
> -f /home/nishant/ubuntu.conf
> /h
On Mon, 2011-10-24 at 10:24 +0200, Ulli Horlacher wrote:
> On Sat 2010-03-20 (21:30), Daniel Lezcano wrote:
>
> > There will be available a kernel patchset in a few weeks making possible
> > to do live migration with the lxc userspace tools (not libvirt), with
> > some restrictions.
>
> We are
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, 201
Commit 92c7f6295518decd3989b2790d75551e7d9a broke the following scipts:
- lxc-setcap
- lxc-setuid
- lxc-create
This patch adds the missing variables to be substitued by the configure
script.
Cheers.
Signed-off-by: Greg Kurz
---
src/lxc/lxc-create.in |1 +
src/lxc/lxc-setcap.in |4
On Wed, 2011-09-07 at 10:38 +0200, Daniel Lezcano wrote:
> On 09/07/2011 02:17 AM, Nikhil Handigol wrote:
> > 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 fo
On Thu, 2011-06-30 at 07:29 -0300, Osvaldo Filho wrote:
> Is there a way to do a installation of FreeBSD on container?
Unlike VM based containers, lxc containers share the kernel with the
host: they allow you to run any linux based distro as long as it's
compatible with the host kernel. Unless the
On Sat, 2011-05-07 at 11:32 +0200, David Touzeau wrote:
> Dear
>
> is there a solution to fix this issue ?
>
See below.
> System: Debian 2.6.26-2-686
> LXC Build: 0.7.4.1
>
> Configure output :
>
> ./configure --prefix=/usr --includedir="\${prefix}/include" --mandir="\
> ${prefix}/share/ma
On Sat, 2011-05-07 at 09:21 +0200, Ulli Horlacher wrote:
> I want to temporary suspend (no shutdown!) a running container (flupp)
> and start another with the same ip (for some tests).
> I thought freezing it is the best way, but:
>
>
> root@vms2:/lxc# lxc -l
> container size (MB)
On Tue, 2011-05-03 at 11:38 -0500, Serge Hallyn wrote:
> Quoting Daniel Lezcano (daniel.lezc...@free.fr):
> > Yes. And I think the positive side effect is we can determine if the
> > pid belongs to the same pid namespace than the current one when the
> > container_init is 1, no ?
>
> Yup. (Presum
struct pid *pid, struct task_struct *task)
{
@@ -354,6 +360,7 @@ int proc_pid_status(struct seq_file *m, struct
pid_namespace *ns,
task_cpus_allowed(m, task);
cpuset_task_status_allowed(m, task);
task_context_switch_counts(m, task);
+ task_vpid(m, task);
return 0;
}
Si
On Tue, 2011-05-03 at 09:47 -0500, Serge Hallyn wrote:
> Quoting ian sison (mailing list) (ian.si...@gmail.com):
> > Hi all -
> >
> > In openvz, a certain sysctl parameter,
> >
> > kernel.pid_ns_hide_child = 1
> >
> > when executed at HN system startup will hide any processes that run
> > inside
On Tue, 2011-05-03 at 18:53 +0800, ian sison (mailing list) wrote:
> Hi all -
>
> In openvz, a certain sysctl parameter,
>
> kernel.pid_ns_hide_child = 1
>
> when executed at HN system startup will hide any processes that run
> inside the running containers from appearing in the output of 'ps'.
On Wed, 2011-04-27 at 08:47 -0500, Serge Hallyn wrote:
> Quoting Christoph Mitasch (cmita...@thomas-krenn.com):
> > Hi,
> >
> > I would really love to see the patch applied to latest Ubuntu natty
> > kernel to have "lxc-attach" working again.
> >
> > Is this on the way?
>
> Natty is closed. Thi
On Thu, 2010-05-13 at 14:22 +0200, Ferenc Wagner wrote:
> I'd say we should setpgrp the container init, forward all signals we
> can to it, and have a configuration option for the set of signals
> which
> should be forwarded to the full process group of the container init.
> Or does it make sense t
24 matches
Mail list logo
