Skip to content

Commit f119f1d

Browse files
GodloveDvsoch
authored andcommitted
bunch of minor tweaks (#138)
1 parent 5db52fe commit f119f1d

File tree

5 files changed

+11
-2
lines changed

5 files changed

+11
-2
lines changed
-16 KB
Binary file not shown.

pages/docs/user-docs/action-exec.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,11 @@ SUPPORT_URL="http://www.debian.org/support"
2626
BUG_REPORT_URL="https://bugs.debian.org/"
2727
$
2828
```
29+
### Printing the OS release for a running instance:
30+
Use the `instance://<instance name>` syntax like so:
31+
```
32+
$ singularity exec instance://my-instance cat /etc/os-release
33+
```
2934

3035
### Special Characters
3136
And properly passing along special characters to the program within the container.

pages/docs/user-docs/build-docker-module.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,10 @@ Registry: http://custom_registry
3333
```
3434
The **Registry** keyword is optional. It will default to `index.docker.io`.
3535
```
36+
Namespace: namespace
37+
```
38+
The **Namespace** keyword is optional. It will default to `library`.
39+
```
3640
IncludeCmd: yes
3741
```
3842
The **IncludeCmd** keyword is optional. If included, and if a `%runscript` is not specified, a Docker `CMD` will take precedence over `ENTRYPOINT` and will be used as a runscript. Note that the `IncludeCmd` keyword is considered valid if it is _not empty_! This means that `IncludeCmd: yes` and `IncludeCmd: no` are identical. In both cases the `IncludeCmd` keyword is not empty, so the Docker `CMD` will take precedence over an `ENTRYPOINT`.

pages/docs/user-docs/docs-instance-stop.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Stopping cow1 instance of /home/ubuntu/GodloveD-lolcow-master.img (PID=20522)
3030

3131
### Stop all running instances
3232
```
33-
$ singularity instance.stop \*
33+
$ singularity instance.stop --all
3434
Stopping cow2 instance of /home/ubuntu/GodloveD-lolcow-master.img (PID=20558)
3535
Stopping hiya instance of /home/ubuntu/vsoch-hello-world-master.img (PID=20595)
3636
```

pages/docs/user-docs/docs-recipes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ A Singularity Recipe is the driver of a custom build, and the starting point for
1515
A Singularity Recipe file is divided into several parts:
1616

1717
1. **Header**: The Header describes the core operating system to build within the container. Here you will configure the base operating system features that you need within your container. Examples of this include, what distribution of Linux, what version, what packages must be part of a core install.
18-
2. **Sections**: The rest of the definition is comprised of sections, sometimes called scriptlets or blobs of data. Each section is defined by a `%` character followed by the name of the particular section. All sections are optional.
18+
2. **Sections**: The rest of the definition is comprised of sections, sometimes called scriptlets or blobs of data. Each section is defined by a `%` character followed by the name of the particular section. All sections are optional. Sections that are executed at build time are executed with the `/bin/sh` interpreter and can accept `/bin/sh` options. Similarly, sections that produce scripts to be executed at runtime can accept options intended for `/bin/sh`
1919

2020
Please see the [examples](https://github.com/singularityware/singularity/tree/master/examples) directory in the [Singularity source code](https://github.com/singularityware/singularity) for some ideas on how to get started.
2121

0 commit comments

Comments
 (0)