diff options
| author | Alexandru Tiniuc <tiniuc.alexandru@gmail.com> | 2017-08-25 13:27:02 +0100 |
|---|---|---|
| committer | Bruce Ashfield <bruce.ashfield@windriver.com> | 2017-08-29 08:42:25 -0400 |
| commit | 7677b8214aec8f92601aae2c431da59a5de9249b (patch) | |
| tree | adbbde7d12b399c5dbd4b11e4b11793cd6f88bf0 | |
| parent | 06bc17d1f0650ad2cb134b09b25133bcd641d473 (diff) | |
| download | meta-virtualization-7677b8214aec8f92601aae2c431da59a5de9249b.tar.gz | |
Added README file
Signed-off-by: Alexandru Tiniuc <tiniuc.alexandru@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
| -rw-r--r-- | recipes-containers/singularity/README | 46 |
1 files changed, 46 insertions, 0 deletions
diff --git a/recipes-containers/singularity/README b/recipes-containers/singularity/README new file mode 100644 index 00000000..582480f8 --- /dev/null +++ b/recipes-containers/singularity/README | |||
| @@ -0,0 +1,46 @@ | |||
| 1 | Singularity is a container platform based on the principle of mobility of | ||
| 2 | compute, and it is designed for use within HPC clusters. For more info see | ||
| 3 | singularity.lbl.gov. | ||
| 4 | |||
| 5 | To test whether the software functions correctly, you can use `singularity | ||
| 6 | selftest`. This is what you would expect to see: | ||
| 7 | |||
| 8 | ~# singularity selftest | ||
| 9 | + sh -c test -f /etc/singularity/singularity.conf (retval=0) OK | ||
| 10 | + test -u /usr/libexec/singularity/bin/action-suid (retval=0) OK | ||
| 11 | + test -u /usr/libexec/singularity/bin/create-suid (retval=0) OK | ||
| 12 | + test -u /usr/libexec/singularity/bin/expand-suid (retval=0) OK | ||
| 13 | + test -u /usr/libexec/singularity/bin/export-suid (retval=0) OK | ||
| 14 | + test -u /usr/libexec/singularity/bin/import-suid (retval=0) OK | ||
| 15 | + test -u /usr/libexec/singularity/bin/mount-suid (retval=0) OK | ||
| 16 | |||
| 17 | You can also pull a container from Docker Hub to prove full functionality | ||
| 18 | (Test was performed on a Raspberry Pi 3, hence the arm32v7 part of the Docker | ||
| 19 | link. Make sure you pull an image which is compatible with your hardware.) | ||
| 20 | For instance: | ||
| 21 | |||
| 22 | ~# singularity pull docker://arm32v7/debian:latest | ||
| 23 | Initializing Singularity image subsystem | ||
| 24 | Opening image file: debian-latest.img | ||
| 25 | Creating 200MiB image | ||
| 26 | Binding image to loop | ||
| 27 | Creating file system within image | ||
| 28 | Image is done: debian-latest.img | ||
| 29 | Docker image path: index.docker.io/arm32v7/debian:latest | ||
| 30 | Cache folder set to /home/root/.singularity/docker | ||
| 31 | [1/1] |===================================| 100.0% | ||
| 32 | Importing: base Singularity environment | ||
| 33 | Importing: /home/root/.singularity/docker/sha256:ed4f1f0d0a0457e7f76ffb25a8d6a193007709dd312b7647cb44fc6979ec4a53.tar.gz | ||
| 34 | Importing: /home/root/.singularity/metadata/sha256:89997b2c16b29c5a3a316e314172ef21b36f67cc3200b1c4d95927f716dbee83.tar.gz | ||
| 35 | Done. Container is at: debian-latest.img | ||
| 36 | ~# singularity shell debian-latest.img | ||
| 37 | Singularity: Invoking an interactive shell within container... | ||
| 38 | |||
| 39 | Singularity debian-latest.img:~> echo "Hello from within the container!" | ||
| 40 | Hello from within the container! | ||
| 41 | Singularity debian-latest.img:~> ls / | ||
| 42 | bin dev home lost+found mnt proc run singularity sys usr | ||
| 43 | boot etc lib media opt root sbin srv tmp var | ||
| 44 | Singularity debian-latest.img:~> exit | ||
| 45 | exit | ||
| 46 | ~# | ||
