GNU bug report logs - #63902
System containers with --network won't start "In procedure canonicalize-path: No such file or directory"

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Edouard Klein <edou <at> rdklein.fr>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#63902: closed (System containers with --network won't start
 "In procedure canonicalize-path: No such file or directory")
Date: Tue, 13 Jun 2023 20:07:02 +0000

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

Your message dated Tue, 13 Jun 2023 22:03:13 +0200
with message-id <87r0qfxh2u.fsf <at> rdklein.fr>
and subject line Re: bug#63902: System containers with --network won't start "In procedure canonicalize-path: No such file or directory"
has caused the debbugs.gnu.org bug report #63902,
regarding System containers with --network won't start "In procedure canonicalize-path: No such file or directory"
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
63902: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63902
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: edk <at> beaver-labs.com
To: bug-guix <bug-guix <at> gnu.org>
Subject: System containers with --network won't start "In procedure
 canonicalize-path: No such file or directory"
Date: Mon, 05 Jun 2023 10:23:49 +0200

Dear Guix developers,

To reproduce the bug, take the example container from the documentation:
https://guix.gnu.org/cookbook/en/html_node/A-Database-Container.html

Create a container from the code:
guix system container os.scm

Try to run the container:
sudo /gnu/store/lsa8k983ap58mw8vcpqph89g27skara4-run-container

it works.

Now, just add --network:

guix system container --network os.scm

Run the container
sudo /gnu/store/zqbhfbkc52ifl7j2xhsr9vr1r2a0dpjg-run-container

it fails (both on a Guix System and on a foreign distro (Arch)) with:


system container is running as PID 9090
WARNING: (guile-user): imported module (guix build utils) overrides core binding `delete'
Run 'sudo guix container exec 9090 /run/current-system/profile/bin/bash --login'
or run 'sudo nsenter -a -t 9090' to get a shell into it.

Backtrace:
           7 (primitive-load "/gnu/store/zqbhfbkc52ifl7j2xhsr9vr1r2a?")
In gnu/build/linux-container.scm:
    300:8  6 (call-with-temporary-directory #<procedure 7f0ccbed7d70?>)
   397:16  5 (_ "/tmp/guix-directory.9y6q6s")
     62:6  4 (call-with-clean-exit #<procedure 7f0ccbee3300 at gnu/b?>)
In unknown file:
           3 (primitive-load "/gnu/store/wk96j04sy1rd4sx86n5y7x1a81y?")
In ice-9/eval.scm:
    619:8  2 (_ #f)
   196:35  1 (_ #f)
In unknown file:
           0 (canonicalize-path "/run/current-system")

ERROR: In procedure canonicalize-path:
In procedure canonicalize-path: No such file or directory


I'm available to help with tests.

Cheers,

Edouard.

[Message part 3 (message/rfc822, inline)]

From: Edouard Klein <edou <at> rdklein.fr>
To: Josselin Poiret <dev <at> jpoiret.xyz>
Cc: 63902-done <at> debbugs.gnu.org, 63902 <at> debbugs.gnu.org
Subject: Re: bug#63902: System containers with --network won't start "In
 procedure canonicalize-path: No such file or directory"
Date: Tue, 13 Jun 2023 22:03:13 +0200

Thank you Josselin, I can indeed confirm that it works now :)


Josselin Poiret <dev <at> jpoiret.xyz> writes:

> [[PGP Signed Part:Undecided]]
> Hi,
>
> edk <at> beaver-labs.com writes:
>
>> ERROR: In procedure canonicalize-path:
>> In procedure canonicalize-path: No such file or directory
>
> This bug should have been fixed by
> 181951207339508789b28ba7cb914f983319920f, can you `guix pull` to update
> guix and retry?
>
> Best,

Previous Next

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