Comments

53 Comments

The feedback questions about #1762 and #1638 were mistakes and there does not seem to be a way to remove them. Please give them the same karma as the other two questions.

The feedback questions about #1762 and #1638 were mistakes and there does not seem to be a way to remove them. Please give them the same karma as the other two questions.

The feedback questions about #1762 and #1638 were mistakes and there does not seem to be a way to remove them. Please give them the same karma as the other two questions.

Ignore the bug numbers 1762 and 1638. Those are supposed to be singularity github pull requests but instead the links and titles are for redhat bugzilla.

karma

Works on EL7.5.

karma

Works for me.

karma

I did a singularity exec using an image in /cvmfs/singularity.opensciencegrid.org both with and without -u, works ok.

karma

I tested with vagrant on the generic/fc27 box, and installed from updates-testing. I tested an exec of an image from /cvmfs/singularity.opensciencegrid.org with and without the -u user mode option, works ok.

karma

I tested this build on el6 and did not find any problems. It installed python34.

karma

I neglected to log in before the last comment. Trying again.

karma

It's working well for me too.

karma

Much better

karma

I tried this out on a EL7.3 system, installing with

yum install https://kojipkgs.fedoraproject.org//packages/singularity/2.2.1/2.el7/x86_64/singularity-2.2.1-2.el7.x86_64.rpm https://kojipkgs.fedoraproject.org//packages/singularity/2.2.1/2.el7/x86_64/singularity-runtime-2.2.1-2.el7.x86_64.rpm

and running with singularity -d shell centos7.img (where centos7.img is a singularity image) and it always ends in

VERBOSE [U=3382,P=2783] sexec.c:95:main() : Invoking SUID sexec: /usr/libexec/singularity/sexec-suid

and returns exit code 255.