Container Support

Singularity supports containers in a few different contexts:

Mesos Containerizer

The default mesos containerizer for processes which sets resource limits/etc. Enabled by adding mesos to the --containerizers argument when running mesos-slave. The mesos containerizer can isolate the task via cpu, memory or other parameters specified using the --isolation flag when starting the mesos slave. Deploys with no containerInfo definition will try to run under this containerizer by default.

Mesos Docker Containerizer

The docker containerizer that ships with Mesos, will manage the starting and stopping of your docker container as well as mapping ports, adding environment variables, and mapping volumes in the container to the Mesos sandbox for that task. You can enable this containerizer by adding docker to the arguments of --containerizers when running mesos-slave.

To use Singularity with the Docker containerizer, add a containerInfo field with a type of DOCKER to the SingularityDeploy object when creating a deploy (without specifying a customExecutorCmd). The Singularity deploy object's containerInfo field mirrors the Mesos containerInfo definition:

  "docker": {
    "image": "library/hello-world",
    "privileged": false,
    "network": "BRIDGE", # Can be BRIDGE, HOST, or NONE. Must be BRIDGE if portMappings are set
    "portMappings": [
        "containerPortType": "FROM_OFFER", # FROM_OFFER or LITERAL
        "containerPort": 0, # If type is FROM_OFFER this is the index of the port assigned by Mesos. (ie 0 -> first assigned port)
        "hostPortType": "FROM_OFFER",
        "hostPort": 0
  "volumes": [ # The sandbox for the task will always be added as a volume at /mnt/mesos/sandbox within the container
      "containerPath": "/etc/example",
      "hostPath": "/etc/example"
      "mode": "RO" # RO or RW


Singularity Executor

The SingularityExecutor also supports running Docker containers, with the added bonuses of the SingularityExecutor like logrotate, S3 upload/download, and thread count monitoring.

To use Docker with the Singularity executor, specify the containerInfo as seen above in the Mesos Docker containerizer example, but also include a customExecutorCmd field in your deploy point to the SingularityExecutor. (This is the same method of using the SingularityExecutor as for normal tasks, just adding containerInfo)

When the SingularityExecutor is given a task with containerInfo of type DOCKER, it will do the following:

  • pull the Docker image
  • download any other specified artifacts from the deploy
  • map all specified environment variables to the container
  • assign and map ports and specified volumes
  • map the Mesos sandbox task directory to /mnt/mesos/sandbox in the container
  • create and start the container, directing output to the configured logFile
  • run a docker stop when receiving a SIGTERM, try to remove the stopped container, and exit with the container's exit code

A few special notes and environment variables that are set:

  • Environment variables:
    • MESOS_SANDBOX: The Mesos sandbox directory as seen inside the container (generally /mnt/mesos/sandbox)
    • LOG_DIR: The log directory that SingularityExecutor will use for logrotating/uploading/etc, generally mapped to /mnt/mesos/sandbox/logs in the container
  • The Docker working directory will be set to the taskAppDirectory in the Mesos sandbox
  • The container name will be a configured prefix (se- by default) and the the task id (SingularityExcutorCleanup uses this to optionally clean up old contaienrs that are managed by Singularity)
  • SingularityExecutor will explicitly try to pull the image (ie, must be from a repository reachable by the slave)

Here is an example deploy you can use with the docker-compose setup to get you started:

  "requestId": "docker-hello-world",
  "id": "1",
  "containerInfo": {
    "type": "DOCKER",
    "docker": {
      "image": "hello-world:latest",
      "privileged": false,
      "network": "HOST",
      "portMappings": []
  "customExecutorCmd": "/usr/local/bin/singularity-executor",
  "resources": {
    "cpus": 1,
    "memoryMb": 1024,
    "numPorts": 1
  "executorData": {
    "cmd": "/hello",
    "embeddedArtifacts": [],
    "externalArtifacts": [],
    "s3Artifacts": [],
    "successfulExitCodes": [
    "user": "root",
    "extraCmdLineArgs": [],
    "loggingExtraFields": {},
    "maxTaskThreads": 2048

results matching ""

    No results matching ""