‘guix pack -f squashfs’ absolute symlinks confuse Singularity 2.x

  • Done
  • quality assurance status badge
Details
One participant
  • Ludovic Courtès
Owner
unassigned
Submitted by
Ludovic Courtès
Severity
normal
L
L
Ludovic Courtès wrote on 19 Mar 2019 10:37
(name . Bug Guix)(address . bug-guix@gnu.org)
87a7hrciib.fsf@inria.fr
Hello,

‘guix pack -f squashfs -S /bin=bin bash …’ produces a file system that
contains symlinks with absolute targets.

Unfortunately, Singularity 2.x erroneously checks for symlink validity
before chroot’ing into the file system. Thus all these absolute
symlinks appear to be dangling (unless the host happens to have those
symlink targets…).

I reported this a while back but this hasn’t been fixed in 2.x (the new
3.x code base doesn’t seem to have this problem):


The effect of this bug is that our images appear to be unusable with
Singularity 2.x, at least if you don’t manually adjust the file system
to fix those symlinks:

Toggle snippet (5 lines)
$ singularity exec bash.sqsh /bin/sh
ERROR : No valid /bin/sh in container
ABORT : Retval = 255

Ludo’.
L
L
Ludovic Courtès wrote on 19 Mar 2019 11:31
Re: bug#34913: ‘guix pack -f squash fs’ absolute symlinks confuse Singularity 2.x
(address . 34913-done@debbugs.gnu.org)
87h8bzb1fq.fsf@gnu.org
Ludovic Courtès <ludovic.courtes@inria.fr> skribis:

Toggle quote (8 lines)
> The effect of this bug is that our images appear to be unusable with
> Singularity 2.x, at least if you don’t manually adjust the file system
> to fix those symlinks:
>
> $ singularity exec bash.sqsh /bin/sh
> ERROR : No valid /bin/sh in container
> ABORT : Retval = 255

Fixed in 427c87d0bdc06cc3ee7fc220fd3ad36084412533.

Ludo’.
Closed
?