Re: mesos slave in docker container

sees all containers prefixed with 'mesos-' as one it is supposed to administer so it is killing itself off since it doesn't match a task that should be running. On Fri, Jun 19, 2015 at 6:35 PM, Tyson Norris tnor...@adobe.commailto:tnor...@adobe.com wrote: Hi - Sorry for the delay, just getting back

mesos slave in docker container

Hi - We are running mesos slave (0.22.0-1.0.ubuntu1404) in a docker container with docker containerizer without problems on ubuntu 14.04 docker host (with lxc-docker pkg etc added). Running the same slave container on RHEL 7.0 docker host, the container exits almost immediately after

Re: docker based executor

of patches that is pending to be merged that will also make recovering tasks when relaunching mesos-slave in a docker works. Currently even with --pid=host when your slave dies your tasks are not able to recover when it restarts. Tim On Sat, Apr 18, 2015 at 10:32 PM, Tyson Norris tnor

Re: docker based executor

and stderr logs. Tim On Fri, Apr 17, 2015 at 11:16 PM, Tyson Norris tnor...@adobe.commailto:tnor...@adobe.com wrote: The sequence I see in the docker.log when my executor is launched is something like: GET /containers/id/json POST /containers/id/wait POST /containers/id/stop GET /containers/id/logs

Re: docker based executor

are expected to communicate back to Mesos slave and implement the protocol between mesos and executor. For a test image like this you want to set the CommandInfo with a ContainerInfo holding the docker image instead. Tim On Sat, Apr 18, 2015 at 12:17 PM, Tyson Norris tnor...@adobe.commailto:tnor

Re: docker based executor

/sh -c”. Thanks Tyson On Apr 18, 2015, at 1:03 PM, Tyson Norris tnor...@adobe.commailto:tnor...@adobe.com wrote: Hi Tim - I am using my own framework - a modified version of mesos-storm, attempting to use docker containers instead of TaskInfo is like: TaskInfo task

Re: docker based executor

, Tyson Norris tnor...@adobe.commailto:tnor...@adobe.com wrote: Hi Tim - Actually, rereading your email: For a test image like this you want to set the CommandInfo with a ContainerInfo holding the docker image instead.” it sounds like you are suggesting running the container as a task command

docker based executor

Hi - I am looking at revving the mesos-storm framework to be dockerized (and simpler). I’m using mesos 0.22.0-1.0.ubuntu1404 mesos master + mesos slave are deployed in docker containers, in case it matters. I have the storm (nimbus) framework launching fine as a docker container, but

Re: docker based executor

then the docker will begin to end the container. -Jason On Apr 17, 2015, at 3:23 PM, Tyson Norris tnor...@adobe.commailto:tnor...@adobe.com wrote: Hi - I am looking at revving the mesos-storm framework to be dockerized (and simpler). I’m using mesos 0.22.0-1.0.ubuntu1404 mesos master + mesos slave

Re: docker based executor

; do echo waiting for something to do something sleep 5 done You can put this in a bash file and run that. If you have a dockerfile would be easier to debug. -Jason On Apr 17, 2015, at 4:24 PM, Tyson Norris tnor...@adobe.commailto:tnor...@adobe.com wrote: Yes, agreed that the command should

Re: docker based executor

...@gmail.com wrote: What do any/all logs say? (syslog) -Jason On Apr 17, 2015, at 7:22 PM, Tyson Norris tnor...@adobe.commailto:tnor...@adobe.com wrote: another interesting fact: I can restart the docker container of my executor, and it runs great. In the test example below, notice the stdout appears

Re: docker based executor

the Mesos protobuf objects in 1-line JSON instead of bazillion line protobuf toString() pseudo-JSON output. Would be nice to create a library out of it.) Would you like to participate in an offline thread mesos-storm refactoring? Thanks! - Erik On Fri, Apr 17, 2015 at 12:23 PM, Tyson Norris