You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Thodoris Zois <zo...@ics.forth.gr> on 2017/09/06 11:41:05 UTC
TASK_FAILED - Mesos Container Images
Hello,
I am using the Mesos Containerizer with Docker Images. The problem is that whenever a container exits my task gets TASK_FAILED because the container exits with ‘1’.
My docker file invokes a shell script via CMD /script.sh.
My protobuff can be found below:
https://pastebin.com/1agjAFdm <https://pastebin.com/1agjAFdm>
The agent log can be found here:
https://pastebin.com/Q6qndVuU <https://pastebin.com/Q6qndVuU>
The stderr and stdout from the UI can be found here:
stdout: https://pastebin.com/SkDDUDDJ <https://pastebin.com/SkDDUDDJ>
stderr: https://pastebin.com/t2TFgQ4G <https://pastebin.com/t2TFgQ4G>
Any help would be appreciated,
Thank you very much!
Zois Theodoros
Re: TASK_FAILED - Mesos Container Images
Posted by Thodoris Zois <zo...@ics.forth.gr>.
No problem! I am glad that you tried to help me.. Thank you!
> On 7 Sep 2017, at 18:21, Olivier Sallou <ol...@irisa.fr> wrote:
>
>
>
> On 09/07/2017 04:58 PM, Thodoris Zois wrote:
>> I am using the Mesos Containerizer and i run docker images. I don’t have any proto DockerInfo.. I use Protos.ContainerInfo and Protos.Image
> oh sorry, though you were using docker containerizer
> I don't know what are limitations for mesos containerizer regarding /proc etc... access and how to override this.
>
>>
>>
>>> On 7 Sep 2017, at 17:48, Olivier Sallou <olivier.sallou@irisa.fr <ma...@irisa.fr>> wrote:
>>>
>>>
>>> On 09/07/2017 04:44 PM, Thodoris Zois wrote:
>>>> Actually my issue is that i want to set some flags on docker run so i can give privileges to the docker image, using —privileged. In the Dockerfile i am using CMD script.sh in which my command fails due to privileges.
>>> in mesos.proto there is in DockerInfo the "privileged" parameter
>>> The "parameters" parameter gives you possibility to specify arbitrary ones but this is not advised for future compatibility (and could depend on docker versions)
>>>>
>>>> Thodoris
>>>>
>>>>> On 7 Sep 2017, at 17:40, Olivier Sallou <olivier.sallou@irisa.fr <ma...@irisa.fr>> wrote:
>>>>>
>>>>>
>>>>>
>>>>> On 09/06/2017 06:40 PM, Thodoris Zois wrote:
>>>>>> Yes you are right, this is the problem. I aso noticed it. Docker image has no privileges so script can't execute this command. Is there any way to use arguments in proto? Or i have to set command to the task? And set shell to true?
>>>>> personally, I set
>>>>> task.command.shell to True
>>>>> and task.command.value = "myscript to execute"
>>>>>
>>>>> "myscript" is the bash commands to execute.
>>>>>
>>>>> This can be used to override default entrypoint if this is your issue
>>>>>
>>>>> Olivier
>>>>>>
>>>>>> Thodoris
>>>>>>
>>>>>>> On 6 Sep 2017, at 18:26, James Peach <jorgar@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>
>>>>>>>
>>>>>>>> On Sep 6, 2017, at 4:41 AM, Thodoris Zois <zois@ics.forth.gr <ma...@ics.forth.gr>> wrote:
>>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> I am using the Mesos Containerizer with Docker Images. The problem is that whenever a container exits my task gets TASK_FAILED because the container exits with ‘1’.
>>>>>>>> My docker file invokes a shell script via CMD /script.sh.
>>>>>>>>
>>>>>>>> My protobuff can be found below:
>>>>>>>> https://pastebin.com/1agjAFdm <https://pastebin.com/1agjAFdm>
>>>>>>>>
>>>>>>>>
>>>>>>>> The agent log can be found here:
>>>>>>>> https://pastebin.com/Q6qndVuU <https://pastebin.com/Q6qndVuU>
>>>>>>>>
>>>>>>>>
>>>>>>>> The stderr and stdout from the UI can be found here:
>>>>>>>> stdout: https://pastebin.com/SkDDUDDJ <https://pastebin.com/SkDDUDDJ>
>>>>>>>>
>>>>>>>> stderr: https://pastebin.com/t2TFgQ4G <https://pastebin.com/t2TFgQ4G>
>>>>>>> /execute_blast.sh: line 4: /proc/sys/vm/drop_caches: Read-only file system
>>>>>>>
>>>>>>>
>>>>>>> Does your task exit when this happens?
>>>>>>>
>>>>>>>
>>>>>
>>>>> --
>>>>> Olivier Sallou
>>>>> IRISA / University of Rennes 1
>>>>> Campus de Beaulieu, 35000 RENNES - FRANCE
>>>>> Tel: 02.99.84.71.95
>>>>>
>>>>> gpg key id: 4096R/326D8438 (keyring.debian.org <http://keyring.debian.org/>)
>>>>> Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
>>>>
>>>
>>> --
>>> Olivier Sallou
>>> IRISA / University of Rennes 1
>>> Campus de Beaulieu, 35000 RENNES - FRANCE
>>> Tel: 02.99.84.71.95
>>>
>>> gpg key id: 4096R/326D8438 (keyring.debian.org <http://keyring.debian.org/>)
>>> Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
>>>
>>
>
> --
> Olivier Sallou
> IRISA / University of Rennes 1
> Campus de Beaulieu, 35000 RENNES - FRANCE
> Tel: 02.99.84.71.95
>
> gpg key id: 4096R/326D8438 (keyring.debian.org <http://keyring.debian.org/>)
> Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
>
>
Re: TASK_FAILED - Mesos Container Images
Posted by Olivier Sallou <ol...@irisa.fr>.
On 09/07/2017 04:58 PM, Thodoris Zois wrote:
> I am using the Mesos Containerizer and i run docker images. I don’t
> have any proto DockerInfo.. I use Protos.ContainerInfo and Protos.Image
oh sorry, though you were using docker containerizer
I don't know what are limitations for mesos containerizer regarding
/proc etc... access and how to override this.
>
>
>> On 7 Sep 2017, at 17:48, Olivier Sallou <olivier.sallou@irisa.fr
>> <ma...@irisa.fr>> wrote:
>>
>>
>> On 09/07/2017 04:44 PM, Thodoris Zois wrote:
>>> Actually my issue is that i want to set some flags on docker run so
>>> i can give privileges to the docker image, using —privileged. In the
>>> Dockerfile i am using CMD script.sh in which my command fails due to
>>> privileges.
>> in mesos.proto there is in DockerInfo the "privileged" parameter
>> The "parameters" parameter gives you possibility to specify arbitrary
>> ones but this is not advised for future compatibility (and could
>> depend on docker versions)
>>>
>>> Thodoris
>>>
>>>> On 7 Sep 2017, at 17:40, Olivier Sallou <olivier.sallou@irisa.fr
>>>> <ma...@irisa.fr>> wrote:
>>>>
>>>>
>>>>
>>>> On 09/06/2017 06:40 PM, Thodoris Zois wrote:
>>>>> Yes you are right, this is the problem. I aso noticed it. Docker
>>>>> image has no privileges so script can't execute this command. Is
>>>>> there any way to use arguments in proto? Or i have to set command
>>>>> to the task? And set shell to true?
>>>> personally, I set
>>>> task.command.shell to True
>>>> and task.command.value = "myscript to execute"
>>>>
>>>> "myscript" is the bash commands to execute.
>>>>
>>>> This can be used to override default entrypoint if this is your issue
>>>>
>>>> Olivier
>>>>>
>>>>> Thodoris
>>>>>
>>>>>> On 6 Sep 2017, at 18:26, James Peach <jorgar@gmail.com
>>>>>> <ma...@gmail.com>> wrote:
>>>>>>
>>>>>>
>>>>>>> On Sep 6, 2017, at 4:41 AM, Thodoris Zois <zois@ics.forth.gr
>>>>>>> <ma...@ics.forth.gr>> wrote:
>>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> I am using the Mesos Containerizer with Docker Images. The
>>>>>>> problem is that whenever a container exits my task gets
>>>>>>> TASK_FAILED because the container exits with ‘1’.
>>>>>>> My docker file invokes a shell script via CMD /script.sh.
>>>>>>>
>>>>>>> My protobuff can be found below:
>>>>>>> https://pastebin.com/1agjAFdm
>>>>>>>
>>>>>>>
>>>>>>> The agent log can be found here:
>>>>>>> https://pastebin.com/Q6qndVuU
>>>>>>>
>>>>>>>
>>>>>>> The stderr and stdout from the UI can be found here:
>>>>>>> stdout: https://pastebin.com/SkDDUDDJ
>>>>>>>
>>>>>>> stderr: https://pastebin.com/t2TFgQ4G
>>>>>> /execute_blast.sh: line 4: /proc/sys/vm/drop_caches: Read-only
>>>>>> file system
>>>>>>
>>>>>>
>>>>>> Does your task exit when this happens?
>>>>>>
>>>>>>
>>>>
>>>> --
>>>> Olivier Sallou
>>>> IRISA / University of Rennes 1
>>>> Campus de Beaulieu, 35000 RENNES - FRANCE
>>>> Tel: 02.99.84.71.95
>>>>
>>>> gpg key id: 4096R/326D8438 (keyring.debian.org
>>>> <http://keyring.debian.org/>)
>>>> Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
>>>
>>
>> --
>> Olivier Sallou
>> IRISA / University of Rennes 1
>> Campus de Beaulieu, 35000 RENNES - FRANCE
>> Tel: 02.99.84.71.95
>>
>> gpg key id: 4096R/326D8438 (keyring.debian.org <http://keyring.debian.org>)
>> Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
>>
>
--
Olivier Sallou
IRISA / University of Rennes 1
Campus de Beaulieu, 35000 RENNES - FRANCE
Tel: 02.99.84.71.95
gpg key id: 4096R/326D8438 (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
Re: TASK_FAILED - Mesos Container Images
Posted by Thodoris Zois <zo...@ics.forth.gr>.
I am using the Mesos Containerizer and i run docker images. I don’t have any proto DockerInfo.. I use Protos.ContainerInfo and Protos.Image
> On 7 Sep 2017, at 17:48, Olivier Sallou <ol...@irisa.fr> wrote:
>
>
> On 09/07/2017 04:44 PM, Thodoris Zois wrote:
>> Actually my issue is that i want to set some flags on docker run so i can give privileges to the docker image, using —privileged. In the Dockerfile i am using CMD script.sh in which my command fails due to privileges.
> in mesos.proto there is in DockerInfo the "privileged" parameter
> The "parameters" parameter gives you possibility to specify arbitrary ones but this is not advised for future compatibility (and could depend on docker versions)
>>
>> Thodoris
>>
>>> On 7 Sep 2017, at 17:40, Olivier Sallou <olivier.sallou@irisa.fr <ma...@irisa.fr>> wrote:
>>>
>>>
>>>
>>> On 09/06/2017 06:40 PM, Thodoris Zois wrote:
>>>> Yes you are right, this is the problem. I aso noticed it. Docker image has no privileges so script can't execute this command. Is there any way to use arguments in proto? Or i have to set command to the task? And set shell to true?
>>> personally, I set
>>> task.command.shell to True
>>> and task.command.value = "myscript to execute"
>>>
>>> "myscript" is the bash commands to execute.
>>>
>>> This can be used to override default entrypoint if this is your issue
>>>
>>> Olivier
>>>>
>>>> Thodoris
>>>>
>>>>> On 6 Sep 2017, at 18:26, James Peach <jorgar@gmail.com <ma...@gmail.com>> wrote:
>>>>>
>>>>>
>>>>>> On Sep 6, 2017, at 4:41 AM, Thodoris Zois <zois@ics.forth.gr <ma...@ics.forth.gr>> wrote:
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I am using the Mesos Containerizer with Docker Images. The problem is that whenever a container exits my task gets TASK_FAILED because the container exits with ‘1’.
>>>>>> My docker file invokes a shell script via CMD /script.sh.
>>>>>>
>>>>>> My protobuff can be found below:
>>>>>> https://pastebin.com/1agjAFdm <https://pastebin.com/1agjAFdm>
>>>>>>
>>>>>>
>>>>>> The agent log can be found here:
>>>>>> https://pastebin.com/Q6qndVuU <https://pastebin.com/Q6qndVuU>
>>>>>>
>>>>>>
>>>>>> The stderr and stdout from the UI can be found here:
>>>>>> stdout: https://pastebin.com/SkDDUDDJ <https://pastebin.com/SkDDUDDJ>
>>>>>>
>>>>>> stderr: https://pastebin.com/t2TFgQ4G <https://pastebin.com/t2TFgQ4G>
>>>>> /execute_blast.sh: line 4: /proc/sys/vm/drop_caches: Read-only file system
>>>>>
>>>>>
>>>>> Does your task exit when this happens?
>>>>>
>>>>>
>>>
>>> --
>>> Olivier Sallou
>>> IRISA / University of Rennes 1
>>> Campus de Beaulieu, 35000 RENNES - FRANCE
>>> Tel: 02.99.84.71.95
>>>
>>> gpg key id: 4096R/326D8438 (keyring.debian.org <http://keyring.debian.org/>)
>>> Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
>>
>
> --
> Olivier Sallou
> IRISA / University of Rennes 1
> Campus de Beaulieu, 35000 RENNES - FRANCE
> Tel: 02.99.84.71.95
>
> gpg key id: 4096R/326D8438 (keyring.debian.org)
> Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
>
Re: TASK_FAILED - Mesos Container Images
Posted by Olivier Sallou <ol...@irisa.fr>.
On 09/07/2017 04:44 PM, Thodoris Zois wrote:
> Actually my issue is that i want to set some flags on docker run so i
> can give privileges to the docker image, using —privileged. In the
> Dockerfile i am using CMD script.sh in which my command fails due to
> privileges.
in mesos.proto there is in DockerInfo the "privileged" parameter
The "parameters" parameter gives you possibility to specify arbitrary
ones but this is not advised for future compatibility (and could depend
on docker versions)
>
> Thodoris
>
>> On 7 Sep 2017, at 17:40, Olivier Sallou <olivier.sallou@irisa.fr
>> <ma...@irisa.fr>> wrote:
>>
>>
>>
>> On 09/06/2017 06:40 PM, Thodoris Zois wrote:
>>> Yes you are right, this is the problem. I aso noticed it. Docker
>>> image has no privileges so script can't execute this command. Is
>>> there any way to use arguments in proto? Or i have to set command to
>>> the task? And set shell to true?
>> personally, I set
>> task.command.shell to True
>> and task.command.value = "myscript to execute"
>>
>> "myscript" is the bash commands to execute.
>>
>> This can be used to override default entrypoint if this is your issue
>>
>> Olivier
>>>
>>> Thodoris
>>>
>>>> On 6 Sep 2017, at 18:26, James Peach <jorgar@gmail.com
>>>> <ma...@gmail.com>> wrote:
>>>>
>>>>
>>>>> On Sep 6, 2017, at 4:41 AM, Thodoris Zois <zois@ics.forth.gr
>>>>> <ma...@ics.forth.gr>> wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> I am using the Mesos Containerizer with Docker Images. The problem
>>>>> is that whenever a container exits my task gets TASK_FAILED
>>>>> because the container exits with ‘1’.
>>>>> My docker file invokes a shell script via CMD /script.sh.
>>>>>
>>>>> My protobuff can be found below:
>>>>> https://pastebin.com/1agjAFdm
>>>>>
>>>>>
>>>>> The agent log can be found here:
>>>>> https://pastebin.com/Q6qndVuU
>>>>>
>>>>>
>>>>> The stderr and stdout from the UI can be found here:
>>>>> stdout: https://pastebin.com/SkDDUDDJ
>>>>>
>>>>> stderr: https://pastebin.com/t2TFgQ4G
>>>> /execute_blast.sh: line 4: /proc/sys/vm/drop_caches: Read-only file
>>>> system
>>>>
>>>>
>>>> Does your task exit when this happens?
>>>>
>>>>
>>
>> --
>> Olivier Sallou
>> IRISA / University of Rennes 1
>> Campus de Beaulieu, 35000 RENNES - FRANCE
>> Tel: 02.99.84.71.95
>>
>> gpg key id: 4096R/326D8438 (keyring.debian.org
>> <http://keyring.debian.org/>)
>> Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
>
--
Olivier Sallou
IRISA / University of Rennes 1
Campus de Beaulieu, 35000 RENNES - FRANCE
Tel: 02.99.84.71.95
gpg key id: 4096R/326D8438 (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
Re: TASK_FAILED - Mesos Container Images
Posted by Thodoris Zois <zo...@ics.forth.gr>.
Actually my issue is that i want to set some flags on docker run so i can give privileges to the docker image, using —privileged. In the Dockerfile i am using CMD script.sh in which my command fails due to privileges.
Thodoris
> On 7 Sep 2017, at 17:40, Olivier Sallou <ol...@irisa.fr> wrote:
>
>
>
> On 09/06/2017 06:40 PM, Thodoris Zois wrote:
>> Yes you are right, this is the problem. I aso noticed it. Docker image has no privileges so script can't execute this command. Is there any way to use arguments in proto? Or i have to set command to the task? And set shell to true?
> personally, I set
> task.command.shell to True
> and task.command.value = "myscript to execute"
>
> "myscript" is the bash commands to execute.
>
> This can be used to override default entrypoint if this is your issue
>
> Olivier
>>
>> Thodoris
>>
>>> On 6 Sep 2017, at 18:26, James Peach <jo...@gmail.com> wrote:
>>>
>>>
>>>> On Sep 6, 2017, at 4:41 AM, Thodoris Zois <zo...@ics.forth.gr> wrote:
>>>>
>>>> Hello,
>>>>
>>>> I am using the Mesos Containerizer with Docker Images. The problem is that whenever a container exits my task gets TASK_FAILED because the container exits with ‘1’.
>>>> My docker file invokes a shell script via CMD /script.sh.
>>>>
>>>> My protobuff can be found below:
>>>> https://pastebin.com/1agjAFdm
>>>>
>>>>
>>>> The agent log can be found here:
>>>> https://pastebin.com/Q6qndVuU
>>>>
>>>>
>>>> The stderr and stdout from the UI can be found here:
>>>> stdout: https://pastebin.com/SkDDUDDJ
>>>>
>>>> stderr: https://pastebin.com/t2TFgQ4G
>>> /execute_blast.sh: line 4: /proc/sys/vm/drop_caches: Read-only file system
>>>
>>>
>>> Does your task exit when this happens?
>>>
>>>
>
> --
> Olivier Sallou
> IRISA / University of Rennes 1
> Campus de Beaulieu, 35000 RENNES - FRANCE
> Tel: 02.99.84.71.95
>
> gpg key id: 4096R/326D8438 (keyring.debian.org <http://keyring.debian.org/>)
> Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
Re: TASK_FAILED - Mesos Container Images
Posted by Olivier Sallou <ol...@irisa.fr>.
On 09/06/2017 06:40 PM, Thodoris Zois wrote:
> Yes you are right, this is the problem. I aso noticed it. Docker image has no privileges so script can't execute this command. Is there any way to use arguments in proto? Or i have to set command to the task? And set shell to true?
personally, I set
task.command.shell to True
and task.command.value = "myscript to execute"
"myscript" is the bash commands to execute.
This can be used to override default entrypoint if this is your issue
Olivier
>
> Thodoris
>
>> On 6 Sep 2017, at 18:26, James Peach <jo...@gmail.com> wrote:
>>
>>
>>> On Sep 6, 2017, at 4:41 AM, Thodoris Zois <zo...@ics.forth.gr> wrote:
>>>
>>> Hello,
>>>
>>> I am using the Mesos Containerizer with Docker Images. The problem is that whenever a container exits my task gets TASK_FAILED because the container exits with ‘1’.
>>> My docker file invokes a shell script via CMD /script.sh.
>>>
>>> My protobuff can be found below:
>>> https://pastebin.com/1agjAFdm
>>>
>>>
>>> The agent log can be found here:
>>> https://pastebin.com/Q6qndVuU
>>>
>>>
>>> The stderr and stdout from the UI can be found here:
>>> stdout: https://pastebin.com/SkDDUDDJ
>>>
>>> stderr: https://pastebin.com/t2TFgQ4G
>> /execute_blast.sh: line 4: /proc/sys/vm/drop_caches: Read-only file system
>>
>>
>> Does your task exit when this happens?
>>
>>
--
Olivier Sallou
IRISA / University of Rennes 1
Campus de Beaulieu, 35000 RENNES - FRANCE
Tel: 02.99.84.71.95
gpg key id: 4096R/326D8438 (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
Re: TASK_FAILED - Mesos Container Images
Posted by Thodoris Zois <zo...@ics.forth.gr>.
Yes you are right, this is the problem. I aso noticed it. Docker image has no privileges so script can't execute this command. Is there any way to use arguments in proto? Or i have to set command to the task? And set shell to true?
Thodoris
> On 6 Sep 2017, at 18:26, James Peach <jo...@gmail.com> wrote:
>
>
>> On Sep 6, 2017, at 4:41 AM, Thodoris Zois <zo...@ics.forth.gr> wrote:
>>
>> Hello,
>>
>> I am using the Mesos Containerizer with Docker Images. The problem is that whenever a container exits my task gets TASK_FAILED because the container exits with ‘1’.
>> My docker file invokes a shell script via CMD /script.sh.
>>
>> My protobuff can be found below:
>> https://pastebin.com/1agjAFdm
>>
>>
>> The agent log can be found here:
>> https://pastebin.com/Q6qndVuU
>>
>>
>> The stderr and stdout from the UI can be found here:
>> stdout: https://pastebin.com/SkDDUDDJ
>>
>> stderr: https://pastebin.com/t2TFgQ4G
>
> /execute_blast.sh: line 4: /proc/sys/vm/drop_caches: Read-only file system
>
>
> Does your task exit when this happens?
>
>
Re: TASK_FAILED - Mesos Container Images
Posted by James Peach <jo...@gmail.com>.
> On Sep 6, 2017, at 4:41 AM, Thodoris Zois <zo...@ics.forth.gr> wrote:
>
> Hello,
>
> I am using the Mesos Containerizer with Docker Images. The problem is that whenever a container exits my task gets TASK_FAILED because the container exits with ‘1’.
> My docker file invokes a shell script via CMD /script.sh.
>
> My protobuff can be found below:
> https://pastebin.com/1agjAFdm
>
>
> The agent log can be found here:
> https://pastebin.com/Q6qndVuU
>
>
> The stderr and stdout from the UI can be found here:
> stdout: https://pastebin.com/SkDDUDDJ
>
> stderr: https://pastebin.com/t2TFgQ4G
/execute_blast.sh: line 4: /proc/sys/vm/drop_caches: Read-only file system
Does your task exit when this happens?