All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano-GANU6spQydw@public.gmane.org>
To: Scott Helvick <crazyscottie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: Isolated shutdown?
Date: Tue, 25 Aug 2009 13:08:56 +0200	[thread overview]
Message-ID: <4A93C648.6050200@free.fr> (raw)
In-Reply-To: <cb541ffb0908250318ud156f27l75de8ed776557505-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Scott Helvick wrote:
> On Tue, Aug 25, 2009 at 4:58 AM, Daniel Lezcano <daniel.lezcano-GANU6spQydw@public.gmane.org>wrote:
>
>   
>> Scott Helvick wrote:
>>
>>     
>>> Hello all,
>>>
>>> I've set up a system container with a mostly-complete filesystem, built
>>> from
>>> scratch.  However, I'm having several minor issues, which leads me to
>>> believe I'm misunderstanding something about how lxc works.  For one
>>> thing,
>>> I find myself unable to kill processes within the container itself
>>> (process
>>> handling is a whole other issue)... yet when I run 'shutdown', it not only
>>> shuts down the container, but also the host!  Somehow I don't think this
>>> was
>>> a design decision. :-)
>>>
>>> Any tips would be appreciated.
>>>
>>>
>>>       
>> It is not yet supported.
>> You can drop PR_CAPBSET_DROP capability for your system container, that
>> will avoid to poweroff your host.
>>     
>
>
> Stupid question; how exactly do I do this, and does it have any side
> effects?   Running 'getpcaps' on the container only reveals:
>
> # getpcaps 2022
> Capabilities for `2022': =
> cap_dac_override,cap_fowner,cap_setpcap,cap_net_admin,cap_net_raw,cap_sys_chroot,cap_sys_admin+ep
>   
Which tools in userspace are you using ?

      parent reply	other threads:[~2009-08-25 11:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-25  9:42 Isolated shutdown? Scott Helvick
     [not found] ` <cb541ffb0908250242g620940bi36f863a7578a0cb7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-08-25  9:58   ` Daniel Lezcano
     [not found]     ` <4A93B5A8.7080104-GANU6spQydw@public.gmane.org>
2009-08-25 10:18       ` Scott Helvick
     [not found]         ` <cb541ffb0908250318ud156f27l75de8ed776557505-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-08-25 11:08           ` Daniel Lezcano [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A93C648.6050200@free.fr \
    --to=daniel.lezcano-ganu6spqydw@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=crazyscottie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.