>>
>> So I did give this interesting lxc-enter-namespace feature a try
>
> Thank you.
This is great, it solves my initial problem quite nicely, and I have given up
on using my own tool :-)
>>
>> So my comments are,
>> - first that defining some even minimal PATH would help;
>
> PATH relati
On Wed, Jan 22, 2014 at 05:35:27PM +0800, Gao feng wrote:
> On 01/21/2014 01:59 AM, Daniel P. Berrange wrote:
> > On Mon, Jan 20, 2014 at 06:53:28PM +0100, Thierry Parmentelat wrote:
> >> Hi
> >>
> >> Well if I need to run anything in the container context, short of entering
> >> it through e.g. ss
On 01/21/2014 01:59 AM, Daniel P. Berrange wrote:
> On Mon, Jan 20, 2014 at 06:53:28PM +0100, Thierry Parmentelat wrote:
>> Hi
>>
>> Well if I need to run anything in the container context, short of entering
>> it through e.g. ssh - hoping this is properly set up - well, I can’t..
>>
>> I am using
On 01/21/2014 05:20 AM, Thierry Parmentelat wrote:
> Hi again
[once again, please don't top-post on technical lists]
>
> So I did give this interesting lxc-enter-namespace feature a try
Thank you.
>
> So my comments are,
> - first that defining some even minimal PATH would help;
PATH relat
Hi again
So I did give this interesting lxc-enter-namespace feature a try
I found a few glitches that I thought might be of interest; I recall that I use
a stock f20 box which probably is already behind as compared to the devel
version
root@warhol ~/thierry # rpm -q libvirt
libvirt-1.1.3.2-1.f
Oh, I had totally failed to spot that one..
Thanks for the tip, I’ll give this a try :-)
On 20 Jan 2014, at 18:59, Daniel P. Berrange wrote:
> On Mon, Jan 20, 2014 at 06:53:28PM +0100, Thierry Parmentelat wrote:
>> Hi
>>
>> Well if I need to run anything in the container context, short of enter
On Mon, Jan 20, 2014 at 06:53:28PM +0100, Thierry Parmentelat wrote:
> Hi
>
> Well if I need to run anything in the container context, short of entering
> it through e.g. ssh - hoping this is properly set up - well, I can’t..
>
> I am using libvirt / lxc to set up a build box; essentially every n
On 01/20/2014 10:53 AM, Thierry Parmentelat wrote:
> Hi
[please don't top-post on technical lists]
>
> Admittedly I’m brain-damaged after having used vservers for too long, and
> their ‘vserver exec command to run’ feature is in my genes now ;)
>
> Now maybe I am the one who is missing someth
Oh, and I was about to forget..
The system I am talking about is PlanetLab, that we now manage with libvirt/lxc
instead of the old vserver-based stuff (although the public testbed still is
vastly vserver-based)
And in that context too, it’s much more efficient for us to plug an incoming
ssh requ
Hi
Well if I need to run anything in the container context, short of entering it
through e.g. ssh - hoping this is properly set up - well, I can’t..
I am using libvirt / lxc to set up a build box; essentially every night I would
spawn a set of fresh VMs of some flavours (fedora18, ubuntu, what
On Mon, Jan 20, 2014 at 11:38:08AM +0100, Thierry Parmentelat wrote:
> Hello there
>
> I am trying to locate the namespaces in place for a given lxc container
> (specifically /proc//ns/*)
>
> And to this end I was wondering what is the recommended way to probe for an
> lxc container's init pid
Hello there
I am trying to locate the namespaces in place for a given lxc container
(specifically /proc//ns/*)
And to this end I was wondering what is the recommended way to probe for an lxc
container's init pid
(mostly I'm after the mnt and pid namespaces, and probably network ones, but
the a
12 matches
Mail list logo
