GNU bug report logs - #65847
system container gathering entropy takes forever

Previous Next

To reply to this bug, email your comments to 65847 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: oscar.quijano <at> use.startmail.com
To: bug-guix <at> gnu.org
Subject: system container gathering entropy takes forever
Date: Sat, 09 Sep 2023 21:40:02 -0000

[Message part 1 (text/plain, inline)]

New containers get stuck with a message similar to the following one:  

  

guile: warning: failed to install locale  

system container is running as PID 85878W  

ARNING: (guile-user): imported module (guix build utils) overrides core
binding `delete'  

Run 'sudo guix container exec 85878 /run/current-system/profile/bin/bash
--login'  

or run 'sudo nsenter -a -t 85878' to get a shell into it.  

  

WARNING: (guile-user): imported module (guix build utils) overrides core
binding `delete'  

making '/gnu/store/gkqmm80naf3zw2n20ml11q7xb2nbnglg-system' the current
system...  

WARNING: (guile-user): imported module (guix build utils) overrides core
binding `delete'  

setting up setuid programs in '/run/setuid-programs'...  

populating /etc from /gnu/store/wigi6gny24gpk2inqy19xswsbplqa6fc-etc...  

WARNING: (guile-user): imported module (guix build utils) overrides core
binding `delete'  

WARNING: (guile-user): imported module (guix build utils) overrides core
binding `delete'  

Please wait while gathering entropy to generate the key pair;  

this may take time...  

  

and the message stays there forever, I have left it running even for more than
half an hour and it doesn't move from there. This is happening even with basic
system container definitions. The previos message was generated when running a
system container with the following system definition:  

  

(use-modules (gnu)  

(gnu services web))  

  

(operating-system  

  

(host-name "container")  

  

(timezone "Europe/Berlin")  

  

(file-systems (cons (file-system  

(device (file-system-label "does-not-matter"))  

(mount-point "/")  

(type "ext4"))  

%base-file-systems))  

  

(bootloader (bootloader-configuration  

(bootloader grub-bootloader)  

(targets '("/dev/sdX"))))  

  

(services %base-services))  

  

  

I also tried sharing /dev/random and /dev/urandom with the host and it still
gets stuck there.  

Any ideas about what could be causing this?  

  

[Message part 2 (text/html, inline)]

Message #8 received at 65847 <at> debbugs.gnu.org (full text, mbox):

From: Jurij <jurij <at> kompot.si>
To: 65847 <at> debbugs.gnu.org
Subject: I think it's running
Date: Mon, 25 Sep 2023 03:46:57 +0200

Your container is running.

Try to reach it, via:
sudo nsenter -a -t <PID> sh

Message #11 received at 65847 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Jurij <jurij <at> kompot.si>
Cc: 65847 <at> debbugs.gnu.org
Subject: Re: bug#65847: system container gathering entropy takes forever
Date: Mon, 12 Feb 2024 15:18:13 +0100

Hi,

Jurij <jurij <at> kompot.si> skribis:

> Your container is running.
>
> Try to reach it, via:
> sudo nsenter -a -t <PID> sh

Indeed.  The problem is that the “entry point” (in Docker parlance) of
images created by ‘guix system image -t docker’ is shepherd (PID 1), and
shepherd never exits.

Ludo’.

Previous Next

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