|
## udocker setup
|
|
## udocker setup
|
|
On cluster there is no possibility to use plain docker. An alternative to it that allows container usage is udocker. It has different command arguments from command line interface, for this reason there are two different sections inside [configuration file](configurastion-file), one for docker and another for udocker.
|
|
On cluster there is no possibility to use plain docker. An alternative to it that allows container usage is udocker. It has different command arguments from command-line interface, for this reason there are two different sections inside [configuration file](configuration-file), one for docker and another for udocker.
|
|
|
|
|
|
There is a snippet that can be used to set up a udocker environment on cluster:
|
|
There is a snippet that can be used to set up a udocker environment on cluster:
|
|
|
|
|
... | @@ -11,7 +11,7 @@ There is a snippet that can be used to setup a udocker environment on cluster: |
... | @@ -11,7 +11,7 @@ There is a snippet that can be used to setup a udocker environment on cluster: |
|
6. exit and enter again inside cluster
|
|
6. exit and enter again inside cluster
|
|
|
|
|
|
## udocker volume directories
|
|
## udocker volume directories
|
|
Normally when you pass a volume to docker it is able to create missing directories related to the passed path. Udocker can not do this, if you write a path inside the [configuration file](configuration-file) and it is not present on disk an exception is raised in which is tell to the user to create all missing directories.
|
|
Normally, when you pass a volume to docker, it is able to create missing directories related to the passed path. Udocker can not do this: if you write a path inside the [configuration file](configuration-file) and it is not present on disk an exception is raised in which is tell to the user to create all missing directories.
|
|
|
|
|
|
Example:
|
|
Example:
|
|
```ini
|
|
```ini
|
... | | ... | |