GNU bug report logs - #34913
‘guix pack -f squashfs’ absolute symlinks confuse Singularity 2.x

Previous Next

Package: guix;

Reported by: Ludovic Courtès <ludovic.courtes <at> inria.fr>

Date: Tue, 19 Mar 2019 09:38:01 UTC

Severity: normal

Done: Ludovic Courtès <ludovic.courtes <at> inria.fr>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 34913 in the body.
You can then email your comments to 34913 AT debbugs.gnu.org in the normal way.

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

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#34913; Package guix. (Tue, 19 Mar 2019 09:38:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to Ludovic Courtès <ludovic.courtes <at> inria.fr>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Tue, 19 Mar 2019 09:38:01 GMT) Full text and rfc822 format available.

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

From: Ludovic Courtès <ludovic.courtes <at> inria.fr>
To: Bug Guix <bug-guix <at> gnu.org>
Subject: ‘guix pack -f squashfs’
 absolute symlinks confuse Singularity 2.x
Date: Tue, 19 Mar 2019 10:37:16 +0100
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):

  https://github.com/sylabs/singularity/issues/1487

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:

--8<---------------cut here---------------start------------->8---
$ singularity exec bash.sqsh /bin/sh
ERROR  : No valid /bin/sh in container
ABORT  : Retval = 255
--8<---------------cut here---------------end--------------->8---

Ludo’.




Reply sent to Ludovic Courtès <ludovic.courtes <at> inria.fr>:
You have taken responsibility. (Tue, 19 Mar 2019 10:32:02 GMT) Full text and rfc822 format available.

Notification sent to Ludovic Courtès <ludovic.courtes <at> inria.fr>:
bug acknowledged by developer. (Tue, 19 Mar 2019 10:32:02 GMT) Full text and rfc822 format available.

Message #10 received at 34913-done <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludovic.courtes <at> inria.fr>
To: 34913-done <at> debbugs.gnu.org
Subject: Re: bug#34913: ‘guix pack -f squashfs’ absolute symlinks confuse Singularity 2.x
Date: Tue, 19 Mar 2019 11:31:21 +0100
Ludovic Courtès <ludovic.courtes <at> inria.fr> skribis:

> 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’.




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Tue, 16 Apr 2019 11:24:04 GMT) Full text and rfc822 format available.

This bug report was last modified 4 years and 338 days ago.

Previous Next


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