libebook | Read info from epub and mobi files | Media library

I had this exact problem and I managed to fix it in Ubuntu 18.04 with singularity version 2.6.1 (I don't think the solution will be much different for you in 2.5.2 though).

Just first a small disclaimer: I'm only using Linux for two weeks now, so, sorry if I'm confusing any terms. I'm new ;)

Steps to take

1. Deinstall earlier versions of Singularity if needed.

2. download tarbell of the correct Singularity version by opening a Terminal and running the following commands:

   VERSION=2.6.1

   wget https://github.com/singularityware/singularity/releases/download/$VERSION/singularity-$VERSION.tar.gz

   tar xvf singularity-$VERSION.tar.gz

3. Now, there should be a folder called singularity-2.6.1 (for me it was placed in Home). Then open the file mount.c placed in /singularity-2.6.1/src/lib/image/squashfs/mount.c (I am not sure if this is the same for v2.5.2 but I assume not that much has changed. We might be out of luck though)

4. In this file find the line of code

   if ( singularity_mount(loop_dev, mount_point, "squashfs", MS_NOSUID|MS_RDONLY|MS_NODEV, "errors=remount-ro") < 0 )

   Change this to

   if ( singularity_mount(loop_dev, mount_point, "squashfs", MS_NOSUID|MS_RDONLY|MS_NODEV, "") < 0 )

   Don't forget to save!

5. Return to the Terminal to install Singularity from the edited installation files by running the commands

   cd singularity-$VERSION

   ./configure --prefix=/usr/local

   make

   sudo make install

For me, the problem was now fixed!

Problem rationale

Apparently, there was a bug in squashfs such that it simply ignored arguments if it didn't know it. When this was fixed earlier this year, it started giving errors when encountering an invalid argument, as happened in our case. (Also explained here https://www.mail-archive.com/debian-kernel@lists.debian.org/msg117435.html) Therefore, removing the unknown argument "errors=remount-ro" fixed the problem.

Since I'm honestly 100% new to this, I'm not sure if it will induce any new errors at other places. However, this is also how this error was basically fixed in a later release of Singularity (https://github.com/hpcng/singularity/pull/4802/files/3f3136be150d9a8f63e58a0b4e39dc8487f1c0dc).

Hope it helped!