[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#948209: marked as done (singularity-container: unable to build Singularity container on WSL2)

Your message dated Mon, 06 Jan 2020 09:23:54 +1100
with message-id <33589084.8M3MqC51IP@deblab>
and subject line Re: Bug#948209: singularity-container: unable to build Singularity container on WSL2
has caused the Debian Bug report #948209,
regarding singularity-container: unable to build Singularity container on WSL2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
948209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948209
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: singularity-container
Version: 3.5.2+ds1-1
Severity: important

I have a Singularity recipe file that has been working for months when
Debian GNU/Linux is installed directly on bare metal.  Today, I tried
to use it on Windows Subsystem for Linux 2 (from Windows 10 Pro for
Workstations Insider Preview, Build 19536), where it unexpectedly
fails.  It is unknown to me whether the problem is or is not due to a
limitation of WSL2.

Setup required in order to be able to reproduce:

Install Windows Subsystem for Linux 2 on a Windows system that
supports it.  Install the Debian GNU/Linux app from the Microsoft
store.  Invoke "debian", edit /etc/apt/sources.list to migrate from
buster to bullseye, perform the update/upgrade/dist-upgrade, install
singularity-container (which unfortunately is not in buster-backports
as I write this).

Then, create a simple recipe named foobar.recipe, containing:

Bootstrap: scratch
%setup
    debootstrap --arch=amd64 --include=build-essential,ca-certificates,dialog,diffuse,keyboard-configuration,less,nano,sudo,wget --variant=minbase --verbose buster $SINGULARITY_ROOTFS http://ftp.us.debian.org/debian/


Once the above is done, here is the reproduction procedure:
1. Launch an Adminstrator Powershell
2. Invoke "debian".
3. Invoke "sudo singularity build output.simg foobar.recipe"

Output observed:
INFO:    Starting build...
FATAL:   container creation failed: failed to mount directory filesystem /tmp/rootfs-ecb3e633-2faf-11ea-ab65-f8b46abb25dc: no such file or directory
FATAL:   while performing build: while running engine: while running /usr/lib/x86_64-linux-gnu/singularity/bin/starter: exit status 255

Expected output:
I expect Singularity to build a close-to-minimal Debian Buster image.


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-19536-Microsoft
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages singularity-container depends on:
ii  ca-certificates              20190110
ii  containernetworking-plugins  0.8.3-2
ii  libc6                        2.29-7
ii  libseccomp2                  2.4.2-2
ii  squashfs-tools               1:4.4-1

Versions of packages singularity-container recommends:
ii  e2fsprogs  1.45.4-1

singularity-container suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Sunday, 5 January 2020 10:56:45 PM AEDT Dave Gomboc wrote:
> Today, I tried
> to use it on Windows Subsystem for Linux 2 (from Windows 10 Pro for
> Workstations Insider Preview, Build 19536), where it unexpectedly
> fails.  It is unknown to me whether the problem is or is not due to a
> limitation of WSL2.

I will not be troubleshooting the problem on unethical operating system.
Personally I consider such effort to be not merely a waste of time but
a disservice to users.

You might try reporting this problem upstream.


> Bootstrap: scratch
> %setup
>     debootstrap --arch=amd64
> --include=build-essential,ca-certificates,dialog,diffuse,keyboard-configur
> ation,less,nano,sudo,wget --variant=minbase --verbose buster
> $SINGULARITY_ROOTFS http://ftp.us.debian.org/debian/

I successfully tried this recipe on Debian hence confirming that it is not
a problem on Debian.

Your recipe could probably be optimised like this:

~~~~
## https://sylabs.io/guides/3.5/user-guide/appendix.html#build-debootstrap
BootStrap: debootstrap
OSVersion: buster
MirrorURL: http://deb.debian.org/debian/
Include: build-essential,ca-certificates,dialog,diffuse,keyboard-configuration,less,nano,sudo,wget
~~~~

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 948209@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

-- 
Regards,
 Dmitry Smirnov.

---

Which country is suffering from too much freedom of speech? Name it, is
there one?

        -- Julian Assange

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: