On Tue, 2014-05-27 at 15:33 +0700, Fajar A. Nugraha wrote:
> On Tue, May 27, 2014 at 2:20 PM, Fajar A. Nugraha wrote:
> > On Mon, May 26, 2014 at 10:22 PM, Michael H. Warfield
> > wrote:
> >> Serge,
> >>
> >> On Thu, 2014-05-15 at 15:31 +, Serge Hallyn wrote:
> >>> Quoting Michael H. Warfiel
On Tue, May 27, 2014 at 2:20 PM, Fajar A. Nugraha wrote:
> On Mon, May 26, 2014 at 10:22 PM, Michael H. Warfield
> wrote:
>> Serge,
>>
>> On Thu, 2014-05-15 at 15:31 +, Serge Hallyn wrote:
>>> Quoting Michael H. Warfield (m...@wittsend.com):
>>> > On Thu, 2014-05-15 at 22:04 +0700, Fajar A.
On Mon, May 26, 2014 at 10:22 PM, Michael H. Warfield wrote:
> Serge,
>
> On Thu, 2014-05-15 at 15:31 +, Serge Hallyn wrote:
>> Quoting Michael H. Warfield (m...@wittsend.com):
>> > On Thu, 2014-05-15 at 22:04 +0700, Fajar A. Nugraha wrote:
>
> [SNIP]
>
>> > > With the unconfied apparmor profi
Serge,
On Thu, 2014-05-15 at 15:31 +, Serge Hallyn wrote:
> Quoting Michael H. Warfield (m...@wittsend.com):
> > On Thu, 2014-05-15 at 22:04 +0700, Fajar A. Nugraha wrote:
[SNIP]
> > > With the unconfied apparmor profile, it works as expected
> > >
> > >
> > >
> > > # lxc-ls -f f20
>
On Thu, 2014-05-15 at 13:11 -0400, CDR wrote:
> I don´t have the command
> lxc-status
> Should I have it?
Oh hell. My bad (one of my local scripts).
Should have been:
lxc-info -n {container}
Sorry about that.
Regards,
Mike
> On Thu, May 15, 2014 at 11:31 AM, Serge Hallyn
> wrote:
> > Quot
I don´t have the command
lxc-status
Should I have it?
On Thu, May 15, 2014 at 11:31 AM, Serge Hallyn wrote:
> Quoting Michael H. Warfield (m...@wittsend.com):
>> On Thu, 2014-05-15 at 22:04 +0700, Fajar A. Nugraha wrote:
>> > On Thu, May 15, 2014 at 9:06 PM, Michael H. Warfield
>> > wrote:
>> >
Quoting Michael H. Warfield (m...@wittsend.com):
> On Thu, 2014-05-15 at 22:04 +0700, Fajar A. Nugraha wrote:
> > On Thu, May 15, 2014 at 9:06 PM, Michael H. Warfield
> > wrote:
> > On Thu, 2014-05-15 at 04:40 -0400, CDR wrote:
> >
> > > The container is started, because I
On Thu, 2014-05-15 at 22:04 +0700, Fajar A. Nugraha wrote:
> On Thu, May 15, 2014 at 9:06 PM, Michael H. Warfield
> wrote:
> On Thu, 2014-05-15 at 04:40 -0400, CDR wrote:
>
> > The container is started, because I am inside it via ssh
> > but I cannot use its consol
On Thu, May 15, 2014 at 9:06 PM, Michael H. Warfield wrote:
> On Thu, 2014-05-15 at 04:40 -0400, CDR wrote:
> > The container is started, because I am inside it via ssh
> > but I cannot use its console
> > lxc-console -n msterfe
> > msterfe is not running
> >
> > I am uploading the configuration a
On Thu, 2014-05-15 at 04:40 -0400, CDR wrote:
> The container is started, because I am inside it via ssh
> but I cannot use its console
> lxc-console -n msterfe
> msterfe is not running
>
> I am uploading the configuration as an attachment
> The container was created from the template, LXC 1.0.3
On Thu, 2014-05-15 at 04:40 -0400, CDR wrote:
> The container is started, because I am inside it via ssh
> but I cannot use its console
> lxc-console -n msterfe
> msterfe is not running
> I am uploading the configuration as an attachment
> The container was created from the template, LXC 1.0.3
>
The container is started, because I am inside it via ssh
but I cannot use its console
lxc-console -n msterfe
msterfe is not running
I am uploading the configuration as an attachment
The container was created from the template, LXC 1.0.3
dpkg --list | grep lxc
ii liblxc1
12 matches
Mail list logo
