This is an outdated version of the HTCondor Manual. You can find current documentation at http://htcondor.org/manual.
next up previous contents index
Next: 2.13 Time Scheduling for Up: 2. Users' Manual Previous: 2.11 Virtual Machine Applications   Contents   Index


2.12 Docker Universe Applications

A docker universe job causes an instantiation of a container, and the job is run within that container, providing all of the benefits of Docker containers to the job.

The docker universe job will only be matched with an execute host that advertises its capability to run docker universe jobs. The details of which container is instantiated are defined by specifying a Docker image with the submit command docker_image.

After submission, the job is treated as a vanilla universe job. Details of file transfer are the same as applied to the vanilla universe. One of the benefits of Docker containers is the isolation they provide. This extends to the file system within a container. The container will not share a file system with either the execute host or the submit host. Therefore, the submit description file should contain the submit command

  should_transfer_files = YES
With this command, all input and output files will be transferred as required to and from the scratch directory mounted as a Docker volume.

If no executable is specified in the submit description file, it is presumed that the Docker container has a default command to run.

When the job completes, or is otherwise evicted, the container will be removed.


next up previous contents index
Next: 2.13 Time Scheduling for Up: 2. Users' Manual Previous: 2.11 Virtual Machine Applications   Contents   Index