MIRRORS/meta-virtualization
1
0
Fork 0
mirror of git://git.yoctoproject.org/meta-virtualization.git synced 2025-07-19 12:50:22 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity
aa558c7824
meta-virtualization/recipes-containers/singularity
History
Martin Jansa aa558c7824 singularity: fix build with python3 
* Fix python3native inherit added in:
  https://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/commit/?id=a1e3f5c92cdee7c4259b7be643bd829ce7c1efa3
  to actually work
* also remove the work arounds for /usr/bin/python being python3
  on the target device
* I haven't tested this in runtime - I don't use it, it was just
  showing that do_configure error in "bitbake world" builds, the
  scripts might need some changes to be really compatible with
  python3, but it was broken already, now it at least builds
* upgrade to new version with
  3c05f06e6a
  would be nice by someone who actually uses this

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
2020-05-21 22:10:19 -04:00
..
singularity singularity: fix build with python3 2020-05-21 22:10:19 -04:00
README Added README file 2017-08-29 08:42:25 -04:00
singularity_git.bb singularity: fix build with python3 2020-05-21 22:10:19 -04:00

README

Singularity is a container platform based on the principle of mobility of compute, and it is designed for use within HPC clusters. For more info see singularity.lbl.gov.

To test whether the software functions correctly, you can use singularity selftest. This is what you would expect to see:

~# singularity selftest

  • sh -c test -f /etc/singularity/singularity.conf (retval=0) OK
  • test -u /usr/libexec/singularity/bin/action-suid (retval=0) OK
  • test -u /usr/libexec/singularity/bin/create-suid (retval=0) OK
  • test -u /usr/libexec/singularity/bin/expand-suid (retval=0) OK
  • test -u /usr/libexec/singularity/bin/export-suid (retval=0) OK
  • test -u /usr/libexec/singularity/bin/import-suid (retval=0) OK
  • test -u /usr/libexec/singularity/bin/mount-suid (retval=0) OK

You can also pull a container from Docker Hub to prove full functionality (Test was performed on a Raspberry Pi 3, hence the arm32v7 part of the Docker link. Make sure you pull an image which is compatible with your hardware.) For instance:

~# singularity pull docker://arm32v7/debian:latest Initializing Singularity image subsystem Opening image file: debian-latest.img Creating 200MiB image Binding image to loop Creating file system within image Image is done: debian-latest.img Docker image path: index.docker.io/arm32v7/debian:latest Cache folder set to /home/root/.singularity/docker [1/1] |===================================| 100.0% Importing: base Singularity environment Importing: /home/root/.singularity/docker/sha256:ed4f1f0d0a0457e7f76ffb25a8d6a193007709dd312b7647cb44fc6979ec4a53.tar.gz Importing: /home/root/.singularity/metadata/sha256:89997b2c16b29c5a3a316e314172ef21b36f67cc3200b1c4d95927f716dbee83.tar.gz Done. Container is at: debian-latest.img ~# singularity shell debian-latest.img Singularity: Invoking an interactive shell within container...

Singularity debian-latest.img:~> echo "Hello from within the container!" Hello from within the container! Singularity debian-latest.img:~> ls / bin dev home lost+found mnt proc run singularity sys usr boot etc lib media opt root sbin srv tmp var Singularity debian-latest.img:~> exit exit ~#