Re: Mesos fetcher in dockerized slave

Yes, I did check inside the container and the csv file was not downloaded as shown also by the app details (see the screenshot below). Are you running your slave with the --docker_mesos_image flag? Can you please provide me the docker run command you are using to run your dockerized slave?

Re: Mesos fetcher in dockerized slave

Can you share exactly how you run the slave in a docker container? Tim On Thu, Dec 17, 2015 at 1:11 PM, Marica Antonacci < marica.antona...@ba.infn.it> wrote: > No, using the socket: > > -v /var/run/docker.sock:/var/run/docker.sock > > > Il giorno 17/dic/2015, alle ore 18:07, tommy xiao

Re: Mesos fetcher in dockerized slave

OK, the problem I spotted is related to the usage of the flag —docker_mesos_image that allows the executor to --docker_mesos_image=VALUE The docker image used to launch this mesos slave instance. If an image is specified, the docker containerizer assumes the slave is running in a docker

Re: Mesos fetcher in dockerized slave

Thank you very much, I’m using a sample application definition file, just for testing purpose: { "id": "test-app", "container": { "type": "DOCKER", "docker": { "image": "libmesos/ubuntu" } }, "cpus": 1, "mem": 512, "uris": [

??????Design for dynamic weights in Mesos

Sorry for my carelessness, correct the link for the design doc as below: https://docs.google.com/document/d/1raTcwzq2Z2He2DIcbzm2g_Ym1YN6wLNP2tbGjUJyAgA/edit?usp=sharing -- Regards! Grady YQ. Wang?? --

Re: Mesos fetcher in dockerized slave

I've tried to use this flag, but cannot really run any container when this flag is set. I've raised this issue here: https://www.mail-archive.com/user@mesos.apache.org/msg04975.html and here: https://github.com/mesosphere/docker-containers/issues/6#issuecomment-155364351 but sadly no one was able

Design for dynamic weights in Mesos

Hi guys, Mesos currently uses a static list of weights, specified when the master is started (via the --weights flag). and it requires that all the masters be rebooted to change the weights as resource allocation priority changes (e.g., a new high-priority framework installed with a new

Re: Mesos fetcher in dockerized slave

The problem happens to me if I don't specify the --docker_mesos_image flag. However, specifying the flag only makes things worse: the task is failed again and agin, but there does exist a container for this task. master and zookeeper is running on host, and slave is running inside a docker image:

Re: Mesos fetcher in dockerized slave

Hi Grzegorz, I’m using this command line for docker run # docker run -d MESOS_HOSTNAME= -e MESOS_IP= -e MESOS_MASTER=zk://:2181,:2181,:2181/mesos -e MESOS_CONTAINERIZERS=docker,mesos -e MESOS_EXECUTOR_REGISTRATION_TIMEOUT=5mins -e MESOS_LOG_DIR=/var/log -e MESOS_docker_mesos_image=mesos-slave

Re: Mesos fetcher in dockerized slave

Hi Tim, looking at the sandbox I can see only the stderr and stout file (see the attached screenshot). If I remove —docker_mesos_image (and therefore the executor is run inside the slave container) the file specified in the URI field is shown in the sandbox. Did you verify that the fetcher is

Re: Mesos fetcher in dockerized slave

HI Marica, Did you see the fetcher invoked at all from the Slave logs? Doesn't seem possible we don't pass down the URI flags and if the fetcher failed the container launch should have failed too. Also another possible situation is that web UI not really showing the exact content of the sandbox,

Re: Mesos fetcher in dockerized slave

Hi Marica, It should work as we fetch all the files before we launch the executor and place them in the sandbox, and we mount the sandbox into that container as well. How did you verify that the file is not downloaded? Tim On Fri, Dec 18, 2015 at 5:26 AM, Marica Antonacci <

Re: Mesos fetcher in dockerized slave

Hi Shuai, You need to specify the --pid=host flag. Tim On Fri, Dec 18, 2015 at 5:19 AM, Shuai Lin wrote: > The problem happens to me if I don't specify the --docker_mesos_image > flag. However, specifying the flag only makes things worse: the task is > failed again and

Re: Role-related configuration in Mesos

Hi, like you write we use roles for a number of pretty loosely coupled concerns (allocation, quota, reservations). While denormalizing the endpoints like you suggest in Proposal (1) simplifies querying information, it limits how that coupling can be evolved in the future (at least if we’d