I added the app with REST API, but nothing changed.
Status stuck in "Deploying"
I also run these commands;

echo 'docker,mesos' > /etc/mesos-slave/containerizers
echo '5mins' > /etc/mesos-slave/executor_registration_timeout

App config is like that

{
   "id":"/test2",
   "cmd":null,
   "args":[

   ],
   "user":null,
   "env":{

   },
   "instances":5,
   "cpus":0.1,
   "mem":128.0,
   "disk":512.0,
   "executor":"",
   "constraints":[

   ],
   "uris":[

   ],
   "storeUrls":[

   ],
   "ports":[
      10001
   ],
   "requirePorts":false,
   "backoffSeconds":1,
   "backoffFactor":1.15,
   "maxLaunchDelaySeconds":3600,
   "container":{
      "type":"DOCKER",
      "volumes":[

      ],
      "docker":{
         "image":"fehmicansaglam/progressed.io",
         "network":null,
         "portMappings":null,
         "privileged":false,
         "parameters":[

         ]
      }
   },
   "healthChecks":[

   ],
   "dependencies":[

   ],
   "upgradeStrategy":{
      "minimumHealthCapacity":1.0,
      "maximumOverCapacity":1.0
   },
   "labels":{

   },
   "version":"2015-02-09T13:55:52.577Z"
}


Thanks


2015-02-09 15:43 GMT+02:00 Dario Rexin <[email protected]>:

> Yes, it’s currently not possible to deploy containers with the web UI.
>
> On 09 Feb 2015, at 14:42, Emre Tekelioğlu <[email protected]>
> wrote:
>
> Hi Dario,
>
> I couldn't find the container section in my Marathon UI when i click New
> App, should i use only REST API to do that?
>
> Regards,
> Emre
>
> 2015-02-09 15:09 GMT+02:00 Dario Rexin <[email protected]>:
>
>> Hi Emre,
>>
>> Mesos and Marathon have full support for running Docker containers, you
>> can just specify them in the app definition, no need to run `docker run …`
>> as a command. Try this app definition instead:
>>
>> {
>>   "id":"/progressed-io",
>>   "instances":5,
>>   "cpus":0.1,
>>   "mem":128.0,
>>   "disk":512.0,
>>   “container”: {
>>      “docker”: {
>>         “image”: “fehmicansaglam/progressed.io"
>>       }
>>   }
>> }
>>
>> Please make sure to start your mesos-slave process with
>> “—containerizers=docker,mesos”
>>
>> Hope this helps.
>>
>> Cheers,
>> Dario
>>
>> On 09 Feb 2015, at 14:02, Emre Tekelioğlu <[email protected]>
>> wrote:
>>
>> Hi Dario
>>
>> Mesos version 0.21.1, Marathon version 0.7.6.
>> App config;
>> {
>>    "id":"/progressed-io",
>>    "cmd":"sudo docker run fehmicansaglam/progressed.io",
>>    "args":null,
>>    "user":null,
>>    "env":{
>>
>>    },
>>    "instances":5,
>>    "cpus":0.1,
>>    "mem":128.0,
>>    "disk":512.0,
>>    "executor":"",
>>    "constraints":[
>>
>>    ],
>>    "uris":[
>>
>>    ],
>>    "storeUrls":[
>>
>>    ],
>>    "ports":[
>>
>>    ],
>>    "requirePorts":false,
>>    "backoffSeconds":1,
>>    "backoffFactor":1.15,
>>    "container":null,
>>    "healthChecks":[
>>
>>    ],
>>    "dependencies":[
>>
>>    ],
>>    "upgradeStrategy":{
>>       "minimumHealthCapacity":1.0
>>    }
>>
>>
>> Thanks,
>> Emre
>>
>> 2015-02-09 14:52 GMT+02:00 Dario Rexin <[email protected]>:
>>
>>> Hi Emre,
>>>
>>> what are the versions of Mesos and Marathon and what does your app
>>> definition look like?
>>>
>>> Cheers,
>>> Dario
>>>
>>> > On 09 Feb 2015, at 13:50, Emre Tekelioğlu <[email protected]>
>>> wrote:
>>> >
>>> > Hi,
>>> > I have a single node mesos cluster on Ubuntu 14.04 host machine, with
>>> one node mesos-master and one node mesos-slave.
>>> > I try to deploy and run my dockerized services with marathon but i
>>> have a weird problem.
>>> >
>>> > For example If i start a new app with 5 instance, only one task start
>>> and the status stuck in "deploying". If i restart the mesos-master, then
>>> the second task start to run.
>>> >
>>> > Each restart for mesos-master cause an increment of a task.
>>> >
>>> > Any idea?
>>> >
>>> > Regards,
>>> > Emre
>>>
>>>
>>
>>
>
>

Reply via email to