From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#20757: "unable to fork" on armhf Date: Sun, 07 Jun 2015 17:46:18 -0400 Message-ID: <87h9qji445.fsf@netris.org> References: <20150607114147.5ad49048@debian-netbook> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52187) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z1iPK-0000Yw-Ng for bug-guix@gnu.org; Sun, 07 Jun 2015 17:47:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z1iPG-0002YT-Mk for bug-guix@gnu.org; Sun, 07 Jun 2015 17:47:06 -0400 Received: from debbugs.gnu.org ([140.186.70.43]:34386) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z1iPG-0002Y8-Je for bug-guix@gnu.org; Sun, 07 Jun 2015 17:47:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1Z1iPF-0002AN-W1 for bug-guix@gnu.org; Sun, 07 Jun 2015 17:47:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20150607114147.5ad49048@debian-netbook> (Efraim Flashner's message of "Sun, 7 Jun 2015 11:41:47 +0300") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Efraim Flashner Cc: 20757@debbugs.gnu.org Efraim Flashner writes: > I have an armhf marsboard that I'm trying to run guix on top of debian. I > started by flashing a debian wheezy image, stripping out most of the > packages, and upgrading to jessie. I installed using the 0.8.2 armhf binary. > `guix pull` failed with the error "unable to fork: Invalid argument", and > likewise `guix build hello` also failed. This is probably because your kernel lacks the necessary features to create the build containers needed by guix-daemon. The above error is printed if the 'clone' system call fails when invoked with the following flags: CLONE_NEWPID | CLONE_NEWNS | CLONE_NEWIPC | CLONE_NEWUTS You need PID namespaces, private mount namespaces, private network namespaces, IPC namespaces, and UTS namespaces. You will also need CONFIG_DEVPTS_MULTIPLE_INSTANCES. We should document this better, but I guess you need at least the following options enabled in your kernel build-time configuration: CONFIG_NAMESPACES=y CONFIG_UTS_NS=y CONFIG_IPC_NS=y CONFIG_USER_NS=y CONFIG_PID_NS=y CONFIG_NET_NS=y CONFIG_DEVPTS_MULTIPLE_INSTANCES=y Mark