all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Omar Tarabai <tarabai@devegypt.com>
To: guix-devel@gnu.org
Subject: GUIX on fedora 14
Date: Tue, 7 Jan 2014 14:57:54 +0100	[thread overview]
Message-ID: <CAK9pnb5iAV20Yf1=jbr58y7ogyK-ue8LgBzfXEFzJbZzZ24-7A@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]

Hello,

I have Guix 0.5 installed on a fedora 14, 2.6.32 kernel.

Running the following:
guix package --verbose -i tar

I get the error:
guix package: error: build failed: unable to fork: Operation not permitted

I traced the error to the clone() operation in build.cc. As mentioned by
Ludovic in a previous conversation with Matthias Wachs, it seems to be a
problem of a missing capability CAP_SYS_ADMIN.
I tried running the daemon as root only or with
--build-users-group=guix-builder but I get the same error. I also tried
isolating the clone operation in a test script to verify the problem, fails
again (running as root).

I tried removing all the CLONE_* flags as recommended by Ludovic, I get the
error:
build error: cannot set loopback interface flags: Permission denied

I assume its because of the missing CLONE_NEWNET

It seems that for some reason on this system, processes started with root
privileges does not get the CAP_SYS_ADMIN capability. I know this is more
of an environment problem than a Guix problem but I was hoping if you guys
have any pointers as what could be the issue.

Thanks a lot,
Omar

[-- Attachment #2: Type: text/html, Size: 1326 bytes --]

             reply	other threads:[~2014-01-07 13:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07 13:57 Omar Tarabai [this message]
2014-01-07 22:55 ` GUIX on fedora 14 Ludovic Courtès
2014-01-08 22:15   ` Omar Tarabai
2014-01-08 22:39     ` Ludovic Courtès
2014-01-09 13:30       ` Omar Tarabai
2014-01-09 23:01         ` Ludovic Courtès

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='CAK9pnb5iAV20Yf1=jbr58y7ogyK-ue8LgBzfXEFzJbZzZ24-7A@mail.gmail.com' \
    --to=tarabai@devegypt.com \
    --cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.