bug#36215: guix system docker-image fails when store items contain non-ascii characters

[Ludovic Courtès]

Hi Björn,

Björn Höfling <address@hidden> skribis:

> On Fri, 14 Jun 2019 23:05:06 +0200
> Björn Höfling <address@hidden> 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’.