unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: 36215-done@debbugs.gnu.org
Subject: bug#36215: guix system docker-image fails when store items contain non-ascii characters
Date: Mon, 17 Jun 2019 12:36:38 +0200	[thread overview]
Message-ID: <87h88ozefd.fsf@gnu.org> (raw)
In-Reply-To: <20190616233449.001ce90d@alma-ubu> ("Björn Höfling"'s message of "Sun, 16 Jun 2019 23:34:49 +0200")

Hi Björn,

Björn Höfling <bjoern.hoefling@bjoernhoefling.de> skribis:

> On Fri, 14 Jun 2019 23:05:06 +0200
> Björn Höfling <bjoern.hoefling@bjoernhoefling.de> wrote:
>
>> qemu-system-x86_64: warning: hub 0 is not connected to host network
>
> [..]
>
>> ERROR: In procedure lstat:
>> In procedure lstat: No such file or directory:
>> "/guixsd-system-root/gnu/store/6w65nzbc3ah30y5kr4zx9rcgknpjr1f5-nss-certs-3.43/etc/ssl/certs/NetLock_Arany_=Class_Gold=_F??tan??s??tv??ny:2.6.73.65.44.228.0.16.pem"
>> ^MESC[Kregistering 177 items [  152.952990] Kernel panic - not
>> syncing: Attempted to kill init! exitcode=0x00000100 [
>
> I looked a bit around the code, added some debugging outputs and found
> out that finally in gnu/build/vm.scm in procedure load-in-linux-vm a
> QEMU VM is started where the docker image will be created in.
>
> To test things, I entered a container with qemu-minimal:
>
> guix environment -N -C --share=/dev/kvm --share=/tmp/.X11-unix/ --ad-hoc coreutils less findutils emacs qemu-minimal nss-certs
>
> And started an existing VM with the store being available over virtfs:
>
> [env] $ qemu-system-x86_64 -m 2048 -smp 2 \
> 		 -boot menu=on \
> 		 -drive file=guixsd0.2018-02-19.qcow2 \
> 		 -drive format=raw,file=swap.img \
> 		 -virtfs local,id=store_dev,path=/gnu/store,security_model=none,mount_tag=store
>
> In that machine, I mounted the fs:
>
> mount -t 9p -o trans=virtio store /mnt
>
> When I then looked at /mnt/...nss-certs.../..., the non-ascii
> characters are looking all good.
>
> I think the encoding-problem is more in the script.

Yes, it looks similar to what 9c941364bfc0120e3ab5c5c4cc71a9a302d59a2b
fixed.

Fixed in ed504cafa23c34bfa1823a4d5abf3ad55205484b.

Thanks!

Ludo’.

  reply	other threads:[~2019-06-17 10:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14 21:05 bug#36215: guix system docker-image fails when store items contain non-ascii characters Björn Höfling
2019-06-16 21:34 ` Björn Höfling
2019-06-17 10:36   ` Ludovic Courtès [this message]
2019-06-18  8:43     ` Björn Höfling

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h88ozefd.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=36215-done@debbugs.gnu.org \
    --cc=bjoern.hoefling@bjoernhoefling.de \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).