Uploaded image for project: 'Marathon'
  1. Marathon
  2. MARATHON-3238

Using container of type MESOS does not start task

    Details

    • Type: Task
    • Status: Resolved
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      Using the following marathon command:

      {
        "id": "mesos-containerizer",
        "cpus": 0.2,
        "mem": 256,
        "instances": 3,
        "args": ["sleep", "100"],
        "container": {
          "type": "MESOS",
          "volumes": [
            {
              "containerPath": "/test",
              "hostPath": "/some/test",
              "mode": "RW"
            }
          ]
        }
      }
      

      I am unable to launch a task. What I expect, is that a task is launched with the standard Mesos containerizer, with this volume. Marathon accepts this as valid JSON. However, Mesos reports the error:

      Container 'xxx' for executor 'xxx' of framework 'xxx' failed to start: None of the enabled containerizers (mesos) could create a container for the provided TaskInfo/ExecutorInfo message.
      

      If you remove the container item from the json, everything works as expected.

      Because Marathon does not log the TaskInfo packet it is sending to mesos, I can't be sure why this is failing.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              GitHub_philwinder Phil Winder (Inactive)
              Team:
              Orchestration Team
              Watchers:
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: