2.4.1 on RHEL6
singularity exec or run will start up with default configuration. I compiled the 'release-2.4' branch and tested it on November 22 as requested, but the code that breaks was added on November 23, the day of the release. Isn't that a bit ridiculous?
ERROR [U=3382,P=22233] singularity_daemon_init() Instance feature is disabled, your kernel is too old
ABORT [U=3382,P=22233] singularity_daemon_init() Retval = 255
Build an rpm on rhel6 or install the version built for OSG, and try to use the exec or run command with any unpacked image. From that link you can also click on "build logs" and "build.log" to see the output of the configure and build process.
No wait I mis-interpreted things, sorry. November 22 was the release date, and that was the timestamp I was looking at. The November 23 commit appears to be a fix for the problem, I am closing this while I investigate. There does not appear to be another issue or pull request about this problem, not that I've been able to find.
For the record, I found the discussion in the google group.
@gmkurtzer Please use pull requests for all your own changes! That will do better travis checking and make it easier for someone to discover why changes were made.
For the record, this is the actual commit that caused the failure and it was slipped in on the day of the release and everybody was not asked to re-test. The one person that was asked to re-test did not reply before the release was cut. Not good quality control!
I fully agree, and maybe to add on this: It would also be nice if the CentOS 6 test in travis actually did something (at least run singularity with a minimal container) instead of only trying to compile it.
Looking at:
https://travis-ci.org/singularityware/singularity/jobs/305994038
I find:
the test suite has not yet been ported to centos6 python, skipping.
That basically means the only thing which is tested for CentOS 6 (which is the main platform for which Singularity is interesting, since for more modern environments, more full-grown container solutions exist) is basic compilation.
Most helpful comment
I fully agree, and maybe to add on this: It would also be nice if the CentOS 6 test in travis actually did something (at least run singularity with a minimal container) instead of only trying to compile it.
Looking at:
https://travis-ci.org/singularityware/singularity/jobs/305994038
I find:
That basically means the only thing which is tested for CentOS 6 (which is the main platform for which Singularity is interesting, since for more modern environments, more full-grown container solutions exist) is basic compilation.