Skip to content

clarified user binding (hopefully) #48

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jan 6, 2017
Merged

clarified user binding (hopefully) #48

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
af77d53
clarified user binding
GodloveD Jan 6, 2017
24d5038
realized that some of my clarification was obfuscation and tried again
GodloveD Jan 6, 2017
1369989
modified the example for successful binding
GodloveD Jan 6, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
realized that some of my clarification was obfuscation and tried again
  • Loading branch information
@GodloveD
GodloveD committed Jan 6, 2017
commit 24d5038afe853dabcba0e8a8b82d51bf0648223e
4 changes: 2 additions & 2 deletions pages/docs/admin-docs/advanced-config.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,9 +44,9 @@ The syntax for this consists of a bind path source and an optional bind path des


### USER BIND CONTROL (boolean, default='yes')
In addition to the system bind points as specified within this configuration file, you may also allow users to define their own bind points inside the container. This feature is used via multiple command line arguments (e.g. `--bind`, `--scratch`, and `--home`) so disabling user bind control will also affect/disable those command line options.
In addition to the system bind points as specified within this configuration file, you may also allow users to define their own bind points inside the container. This feature is used via multiple command line arguments (e.g. `--bind`, `--scratch`, and `--home`) so disabling user bind control will also disable those command line options.

Singularity will automatically disable this feature if the host does not support the prctl option `PR_SET_NO_NEW_PRIVS`. In addition, `enable overlay` must be set to `yes` and the host system must support overlayFS (generally kernel versions 3.18 and later).
Singularity will automatically disable this feature if the host does not support the prctl option `PR_SET_NO_NEW_PRIVS`. In addition, `enable overlay` must be set to `yes` and the host system must support overlayFS (generally kernel versions 3.18 and later) for users to bind host directories to bind points that do not already exist in the container.


## Logging
Expand Down
6 changes: 5 additions & 1 deletion pages/docs/user-docs/docs-bind-paths.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,11 @@ The system administrator has the ability to define what bind points will be incl


#### User defined bind points
If the system administrator has enabled user control of binds and file system overlays (via `user bind control = yes` and `enable overlay = yes` in `/etc/singularity/singularity.conf`), you will be able to request your own bind points within your container processes. The most typical example of this is the `--bind` option and here is an example binding `/tmp` to `/scratch` (which again does not exist within the container). This feature may not be supported on older host systems:
If the system administrator has enabled user control of binds (via `user bind control = yes` in `/etc/singularity/singularity.conf`), you will be able to request your own bind points within your container.

Further, if the administrator has enabled the user of file system overlays (via `enable overlay = yes` in `/etc/singularity/singularity.conf`), you can bind host system directories to directories that do not exist within the container. Singularity will dynamically create the necessary bind points in your container on demand. This feature may not be supported on older host systems.

Here's an example of using the `--bind` option and binding `/tmp` to `/scratch` (which again does not exist within the container):

```bash
$ singularity shell -B /tmp:/scratch /tmp/Centos7-ompi.img
Expand Down