If you have steps that use both script and container actions, the container actions will run as
sibling containers on the same network with the same volume mounts.
Sets an array of volumes for the container to use.
You can use volumes to share data between services or other steps in a job.
You can specify named Docker volumes, anonymous Docker volumes, or bind mounts on the host.
To specify a volume, you specify the source and destination path: :
The is a volume name or an absolute path on the host machine, and
is an absolute path in the container.
Returns the relative, descendent directory path between this module and other.
Throws if no such path exists.
For example, if module mod1 has path /dir1/mod1.pkl, and module mod2 has path
/dir1/dir2/dir3/mod2.pkl, then mod1.relativePathTo(mod2) will return
List("dir2", "dir3").
A common use case is to compute the directory path between a template located at the root of a
hierarchy (say rootModule.pkl) and the currently evaluated module (accessible via the
module keyword):
Use
jobs.<job_id>.containerto create a container to run any steps in a job that don't already specify a container.