Thanks for pointing out the significance of the order, Connor. Very good to know.
On August 27, 2014 at 12:15:07 PM, Connor Doyle ([email protected]) wrote: Hi Eran, that's correct. Mesos supports multiple containerizers now. The order they are listed is significant; as listed the Docker containerizer will pass on the TaskInfo if the ContainerInfo is not set or if the container type is not DOCKER. -- Connor On Aug 27, 2014, at 9:09, Eran Chinthaka Withana <[email protected]> wrote: Thanks Frank for these instructions. I will have to wait for marathon release to use this (hopefully that will happen soon) A n00b question from me here. I noticed that we can now set "--containerizers=docker,mesos". Does this mean mesos slaves will now support both docker type and old containers? If we don't mention "container" section in the marathon request[1], will it work using standard lxc? { "container": { "type": "DOCKER", "docker": { "image": "libmesos/ubuntu" } }, "id": "ubuntu", "instances": "1", "cpus": "0.5", "mem": "128", "uris": [], "cmd": "while sleep 10; do date -u +%T; done" } Thanks, Eran Chinthaka Withana On Tue, Aug 26, 2014 at 11:06 PM, Frank Hinek <[email protected]> wrote: Working here as well. Thanks for the assist Tim! Put together a post on the steps for my own reference: http://frankhinek.com/deploy-docker-containers-on-mesos-0-20/ On August 26, 2014 at 4:39:38 PM, Ray Rodriguez ([email protected]) wrote: Thanks Tim works great. Cheers! On Tue, Aug 26, 2014 at 4:31 PM, Tim Chen <[email protected]> wrote: Hi Ray, Sorry the tutorial is not yet up to date too, once we have Marathon 0.7 released the tutorial will be updated as well. Here is one example for running the image: { "id": "inky", "container": { "docker": { "image": "mesosphere/inky" }, "type": "DOCKER", "volumes": [] }, "args": ["hello"], "cpus": 0.2, "mem": 32.0, "instances": 1 } You can also provide a "cmd" string as well. Tim On Tue, Aug 26, 2014 at 11:28 AM, Ray Rodriguez <[email protected]> wrote: I'm running marathon HEAD 0.7.0 against mesos 0.20.0. My mesos slaves are running with the command line flag --containerizers=docker,mesos and --isolation=cgroups/cpu,cgroups/mem When trying to run the example listed here: http://mesosphere.io/learn/run-docker-on-mesosphere-cluster/ I get the following in the sandbox stderr/stdout stdout: Shutting down stderr: I0826 18:12:48.983397 28817 exec.cpp:132] Version: 0.20.0 I0826 18:12:48.985131 28843 exec.cpp:379] Executor asked to shutdown On Tue, Aug 26, 2014 at 2:15 PM, Frank Hinek <[email protected]> wrote: Thanks for the tip! Building Marathon from latest master at the moment to test. On August 26, 2014 at 1:47:20 PM, Tim Chen ([email protected]) wrote: Hi Frank, Yes you need Marathon 0.7 which we are working on to release soon. In the mean time if you want you can grab latest master to experiment with. Thanks! Tim On Tue, Aug 26, 2014 at 10:41 AM, Frank Hinek <[email protected]> wrote: I did run through that example but it fails every time. Perhaps it is because Marathon 0.6.1 doesn’t yet support the new capabilities in Mesos 0.20.0. curl -X POST -H "Content-Type: application/json" http://127.0.0.1:8080/v2/apps [email protected] nullvagrant@vagrant-ubuntu-trusty-64:/tmp$ I0826 17:23:25.071254 1742 slave.cpp:1002] Got assigned task ubuntu.afa18986-2d45-11e4-8e47-56847afe9799 for framework 20140826-170643-251789322-5050-1532-0000 I0826 17:23:25.072319 1742 slave.cpp:1112] Launching task ubuntu.afa18986-2d45-11e4-8e47-56847afe9799 for framework 20140826-170643-251789322-5050-1532-0000 I0826 17:23:25.073552 1736 docker.cpp:782] No container info found, skipping launch I0826 17:23:25.074030 1742 slave.cpp:1222] Queuing task 'ubuntu.afa18986-2d45-11e4-8e47-56847afe9799' for executor ubuntu.afa18986-2d45-11e4-8e47-56847afe9799 of framework '20140826-170643-251789322-5050-1532-0000 E0826 17:23:25.074518 1742 slave.cpp:2491] Container '01966efd-f521-4f54-87e4-f84aa9adcfa9' for executor 'ubuntu.afa18986-2d45-11e4-8e47-56847afe9799' of framework '20140826-170643-251789322-5050-1532-0000' failed to start: TaskInfo/ExecutorInfo not supported E0826 17:23:25.074937 1742 slave.cpp:2577] Termination of executor 'ubuntu.afa18986-2d45-11e4-8e47-56847afe9799' of framework '20140826-170643-251789322-5050-1532-0000' failed: No container found E0826 17:23:25.075564 1742 slave.cpp:2863] Failed to unmonitor container for executor ubuntu.afa18986-2d45-11e4-8e47-56847afe9799 of framework 20140826-170643-251789322-5050-1532-0000: Not monitored I0826 17:23:25.076370 1742 slave.cpp:2087] Handling status update TASK_FAILED (UUID: 0da7c07d-aeb3-4aa3-a457-0dfcf0243914) for task ubuntu.afa18986-2d45-11e4-8e47-56847afe9799 of framework 20140826-170643-251789322-5050-1532-0000 from @0.0.0.0:0 E0826 17:23:25.076938 1742 slave.cpp:2204] Failed to update resources for container 01966efd-f521-4f54-87e4-f84aa9adcfa9 of executor ubuntu.afa18986-2d45-11e4-8e47-56847afe9799 running task ubuntu.afa18986-2d45-11e4-8e47-56847afe9799 on status update for terminal task, destroying container: No container found I0826 17:23:25.077309 1737 status_update_manager.cpp:320] Received status update TASK_FAILED (UUID: 0da7c07d-aeb3-4aa3-a457-0dfcf0243914) for task ubuntu.afa18986-2d45-11e4-8e47-56847afe9799 of framework 20140826-170643-251789322-5050-1532-0000 I0826 17:23:25.077424 1737 status_update_manager.cpp:373] Forwarding status update TASK_FAILED (UUID: 0da7c07d-aeb3-4aa3-a457-0dfcf0243914) for task ubuntu.afa18986-2d45-11e4-8e47-56847afe9799 of framework 20140826-170643-251789322-5050-1532-0000 to [email protected]:5050 I0826 17:23:25.094221 1741 status_update_manager.cpp:398] Received status update acknowledgement (UUID: 0da7c07d-aeb3-4aa3-a457-0dfcf0243914) for task ubuntu.afa18986-2d45-11e4-8e47-56847afe9799 of framework 20140826-170643-251789322-5050-1532-0000 I0826 17:23:25.094329 1741 slave.cpp:2729] Cleaning up executor 'ubuntu.afa18986-2d45-11e4-8e47-56847afe9799' of framework 20140826-170643-251789322-5050-1532-0000 I0826 17:23:25.094429 1741 slave.cpp:2804] Cleaning up framework 20140826-170643-251789322-5050-1532-0000 I0826 17:23:25.094467 1741 gc.cpp:56] Scheduling '/tmp/mesos/slaves/20140826-171545-251789322-5050-1258-0/frameworks/20140826-170643-251789322-5050-1532-0000/executors/ubuntu.afa18986-2d45-11e4-8e47-56847afe9799/runs/01966efd-f521-4f54-87e4-f84aa9adcfa9' for gc 6.99999890749926days in the future I0826 17:23:25.094507 1741 gc.cpp:56] Scheduling '/tmp/mesos/slaves/20140826-171545-251789322-5050-1258-0/frameworks/20140826-170643-251789322-5050-1532-0000/executors/ubuntu.afa18986-2d45-11e4-8e47-56847afe9799' for gc 6.99999890716444days in the future I0826 17:23:25.094528 1741 gc.cpp:56] Scheduling '/tmp/mesos/slaves/20140826-171545-251789322-5050-1258-0/frameworks/20140826-170643-251789322-5050-1532-0000' for gc 6.99999890679407days in the future I0826 17:23:25.094544 1741 status_update_manager.cpp:282] Closing status update streams for framework 20140826-170643-251789322-5050-1532-0000 On August 26, 2014 at 1:34:37 PM, Jeremy Jongsma ([email protected]) wrote: Mesosphere has updated docs to reflect 0.20, note the "container" configuration field: http://mesosphere.io/learn/run-docker-on-mesosphere-cluster/ On Tue, Aug 26, 2014 at 12:30 PM, Frank Hinek <[email protected]> wrote: Does anyone know of any example that shows how to launch a Docker container under Mesos 0.20.0? I was reading through the details here but unless I develop my own framework it isn’t clear how to start a new container on a Mesos Slave. https://github.com/apache/mesos/blob/master/docs/docker-containerizer.md
