GNU bug report logs - #20757
"unable to fork" on armhf

Previous Next

Full log

View this message in rfc822 format

From: Mark H Weaver <mhw <at> netris.org>
To: Efraim Flashner <efraim <at> flashner.co.il>
Cc: 20757 <at> debbugs.gnu.org
Subject: bug#20757: "unable to fork" on armhf
Date: Sun, 07 Jun 2015 17:46:18 -0400

Efraim Flashner <efraim <at> flashner.co.il> 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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.