All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt-XAri/EZa3C4vJsYlp49lxw@public.gmane.org>
To: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: lxc-start: Invalid argument - failed to remove CAP_SYS_BOOT capability
Date: Tue, 10 Nov 2009 09:37:30 +0300	[thread overview]
Message-ID: <4AF90A2A.2010601@msgid.tls.msk.ru> (raw)

The message in $subj is displayed (and the utility fails) when
trying to start a container on any of my systems.  I traced it
to failing prctl(PR_CAPBSET_DROP, CAP_SYS_BOOT).  According to
the manpage:

   The call fails with the error: EPERM if the calling thread does
   not have the CAP_SETPCAP; EINVAL if arg2 does not represent a
   valid capability; or EINVAL if file capabilities are not
   enabled in the kernel, in which case bounding sets are not sup‐
   ported.

and the corresponding kernel config is SECURITY_FILE_CAPABILITIES,
which is in "Security options" menu named "File POSIX Capabilities".

This is a config option that's not checked by lxc-checkconfig, but
since not setting it entirely prevents lxc from working, I think it
should be checked too.  In any way, I don't think I've seen any
references to that option anywhere.

So here it goes, if not only for reference so that others who will
come to this issue in the future will know what to do.

Thanks!

/mjt
_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers

             reply	other threads:[~2009-11-10  6:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10  6:37 Michael Tokarev [this message]
     [not found] ` <4AF90A2A.2010601-Gdu+ltImwkhes2APU0mLOQ@public.gmane.org>
2009-11-10 20:03   ` lxc-start: Invalid argument - failed to remove CAP_SYS_BOOT capability Daniel Lezcano

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=4AF90A2A.2010601@msgid.tls.msk.ru \
    --to=mjt-xari/eza3c4vjsylp49lxw@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@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.