tar issue about docker2singularity HOT 14 CLOSED

True. My previous solution can still sometimes failed. Eventually I used this "tar" script instead:

#!/bin/bash
set -e

ORIGINAL_ARGS=("$@")
TRIMMED_ARGS=()
for arg; do
  if [ $arg != "--ignore-failed-read" ]; then
    TRIMMED_ARGS+=($arg)
  fi
done

/usr/bin/tar ${TRIMMED_ARGS[@]}

from docker2singularity.

This only started happening when I upgraded to the latest singularity2docker today. The previous version I was using worked fine.

To fix I rolled back to version 2.3.

docker pull singularityware/docker2singularity:v2.3

and using docker2singularity:v2.3 to convert my docker image.

from docker2singularity.

I got the same error. Found a solution from this thread: coreos/bugs#1095
Accordingly I manage to fix it by adding to the RUN:

apk add --update libarchive-tools && \
apk del tar && \
ln -sf $(which bsdtar) /usr/bin/tar

and rebuild the image. It works well for me.

from docker2singularity.

+1

from docker2singularity.

I have the same issue on my Macs. Mojave.

from docker2singularity.

Is this for docker images that were created on a Mac, or is it true wherever this gets run?

from docker2singularity.

This is true wherever the image was created i.e. it does not matter if it is pulled from dockerhub or built locally on a Mac.

from docker2singularity.

I followed the instructions on the other thread. I created my own docker2singularity container using the bsdtar package, replaced the normal Linux tar with a shell script that would strip out some parameters that bsdtar couldn't handle, and then exec bsdtar.

from docker2singularity.

I encountered this issue on Mac, but this problem disappeared on a Docker installed in a CentOS7 VM. Maybe the problem is kernel related as well.

from docker2singularity.

I'm also encountering this issue on OS X Mojave. I've incorporated @akialbert's fixes in a container (jmansour/docker2singularity).

from docker2singularity.

hey everyone apologies I haven't been watching the repository and missed this entire thread! I've just updated the build for version 3.1, and have a few questions for moving forward:

• what versions/s do you need supported?
• is there a solution that would work across OS / architecture that we could implement?

I'd like to put in changes to address your issue - worst case (if the second point is a "no") is that we have a branch / tag for macos. Let me know.

from docker2singularity.

Can anyone comment if this is still an issue? If so, which branches?

from docker2singularity.

The v3.1 release seemed to resolve this issue for the problematic Docker images I had encountered.

from docker2singularity.

Cool, thanks @nathanweeks. I'm going to close the issue for now - if anyone that needs an older version runs into issues, please ping me and I'll get to it right away.

from docker2singularity.