[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mesos-user
Subject:    Re: Killing Docker containers
From:       Ryan Thomas <r.n.thomas () gmail ! com>
Date:       2014-10-15 19:34:44
Message-ID: CANbyX1X4gc7HdamRVjMFvp2hbwFYRauYAg978gV0mT6p3F9CeA () mail ! gmail ! com
[Download RAW message or body]

Latest review is here https://reviews.apache.org/r/26736/ had to update due
to style failures.

Cheers,

Ryan

On Thursday, 16 October 2014, Scott Rankin <srankin@crsinc.com> wrote:

>  Thanks, Ryan.  That solution sounds perfect.
>
>   From: Ryan Thomas <r.n.thomas@gmail.com
> <javascript:_e(%7B%7D,'cvml','r.n.thomas@gmail.com');>>
> Reply-To: "user@mesos.apache.org
> <javascript:_e(%7B%7D,'cvml','user@mesos.apache.org');>" <
> user@mesos.apache.org
> <javascript:_e(%7B%7D,'cvml','user@mesos.apache.org');>>
> Date: Tuesday, October 14, 2014 at 5:19 PM
> To: "user@mesos.apache.org
> <javascript:_e(%7B%7D,'cvml','user@mesos.apache.org');>" <
> user@mesos.apache.org
> <javascript:_e(%7B%7D,'cvml','user@mesos.apache.org');>>
> Subject: Re: Killing Docker containers
>
>   The docker stop command will attempt to kill the container if it
> doesn't stop in 10 seconds by default. I think we should be using this with
> the -t flag to control the time between stop and kill rather than just
> using kill.
>
>  I'll try to submit a patch.
>
>  Cheers,
>
>  ryan
>
> On 15 October 2014 05:37, Scott Rankin <srankin@crsinc.com
> <javascript:_e(%7B%7D,'cvml','srankin@crsinc.com');>> wrote:
>
>>  Hi All,
>>
>>  I'm working on prototyping Mesos+Marathon for our services platform,
>> using apps deployed as Docker containers.  Our applications register
>> themselves with our service discovery framework on startup and un-register
>> themselves when they shut down (assuming they shut down reasonably
>> gracefully).  What I'm finding is that when Mesos shuts down a docker
>> container, it uses "docker kill" as opposed to "docker stop".  I can see
>> the reasoning behind this, but it causes a problem in that the container
>> doesn't get a chance to clean up after itself.
>>
>>  Is this something that might be addressed?  Perhaps by trying docker
>> stop and then running kill if it doesn't shut down after 30 seconds or
>> something?
>>
>>  Thanks,
>> Scott
>>
>> This email message contains information that Corporate Reimbursement
>> Services, Inc. considers confidential and/or proprietary, or may later
>> designate as confidential and proprietary. It is intended only for use of
>> the individual or entity named above and should not be forwarded to any
>> other persons or entities without the express consent of Corporate
>> Reimbursement Services, Inc., nor should it be used for any purpose other
>> than in the course of any potential or actual business relationship with
>> Corporate Reimbursement Services, Inc. If the reader of this message is not
>> the intended recipient, or the employee or agent responsible to deliver it
>> to the intended recipient, you are hereby notified that any dissemination,
>> distribution, or copying of this communication is strictly prohibited. If
>> you have received this communication in error, please notify sender
>> immediately and destroy the original message.
>>
>> Internal Revenue Service regulations require that certain types of
>> written advice include a disclaimer. To the extent the preceding message
>> contains advice relating to a Federal tax issue, unless expressly stated
>> otherwise the advice is not intended or written to be used, and it cannot
>> be used by the recipient or any other taxpayer, for the purpose of avoiding
>> Federal tax penalties, and was not written to support the promotion or
>> marketing of any transaction or matter discussed herein.
>>
>
>   This email message contains information that Corporate Reimbursement
> Services, Inc. considers confidential and/or proprietary, or may later
> designate as confidential and proprietary. It is intended only for use of
> the individual or entity named above and should not be forwarded to any
> other persons or entities without the express consent of Corporate
> Reimbursement Services, Inc., nor should it be used for any purpose other
> than in the course of any potential or actual business relationship with
> Corporate Reimbursement Services, Inc. If the reader of this message is not
> the intended recipient, or the employee or agent responsible to deliver it
> to the intended recipient, you are hereby notified that any dissemination,
> distribution, or copying of this communication is strictly prohibited. If
> you have received this communication in error, please notify sender
> immediately and destroy the original message.
>
> Internal Revenue Service regulations require that certain types of written
> advice include a disclaimer. To the extent the preceding message contains
> advice relating to a Federal tax issue, unless expressly stated otherwise
> the advice is not intended or written to be used, and it cannot be used by
> the recipient or any other taxpayer, for the purpose of avoiding Federal
> tax penalties, and was not written to support the promotion or marketing of
> any transaction or matter discussed herein.
>

[Attachment #3 (text/html)]

Latest review is here  <a \
href="https://reviews.apache.org/r/26736/">https://reviews.apache.org/r/26736/</a>  \
had to update due to style failures.  \
<div><br></div><div>Cheers,</div><div><br></div><div>Ryan  <span></span><br><br>On \
Thursday, 16 October 2014, Scott Rankin &lt;<a \
href="mailto:srankin@crsinc.com">srankin@crsinc.com</a>&gt; wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">



<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
 <div>Thanks, Ryan.   That solution sounds perfect.   </div>
<div><br>
</div>
<span>
<div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium \
none;BORDER-LEFT:medium \
none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt \
solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt"> <span style="font-weight:bold">From: \
</span>Ryan Thomas &lt;<a \
href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;r.n.thomas@gmail.com&#39;);" \
target="_blank">r.n.thomas@gmail.com</a>&gt;<br> <span \
style="font-weight:bold">Reply-To: </span>&quot;<a \
href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;user@mesos.apache.org&#39;);" \
target="_blank">user@mesos.apache.org</a>&quot; &lt;<a \
href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;user@mesos.apache.org&#39;);" \
target="_blank">user@mesos.apache.org</a>&gt;<br> <span \
style="font-weight:bold">Date: </span>Tuesday, October 14, 2014 at 5:19 PM<br> <span \
style="font-weight:bold">To: </span>&quot;<a \
href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;user@mesos.apache.org&#39;);" \
target="_blank">user@mesos.apache.org</a>&quot; &lt;<a \
href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;user@mesos.apache.org&#39;);" \
target="_blank">user@mesos.apache.org</a>&gt;<br> <span \
style="font-weight:bold">Subject: </span>Re: Killing Docker containers<br> </div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">The docker stop command will attempt to kill the container if it \
doesn&#39;t stop in 10 seconds by default. I think we should be using this with the \
-t flag to control the time between stop and kill rather than just using kill. \
<div><br> </div>
<div>I&#39;ll try to submit a patch.</div>
<div><br>
</div>
<div>Cheers,</div>
<div><br>
</div>
<div>ryan</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 15 October 2014 05:37, Scott Rankin <span \
dir="ltr">&lt;<a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;srankin@crsinc.com&#39;);" \
target="_blank">srankin@crsinc.com</a>&gt;</span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> <div \
style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
 <div>Hi All,</div>
<div><br>
</div>
<div>I'm working on prototyping Mesos+Marathon for our services platform, using apps \
deployed as Docker containers.   Our applications register themselves with our \
service discovery framework on startup and un-register themselves when they shut down \
(assuming  they shut down reasonably gracefully).   What I'm finding is that when \
Mesos shuts down a docker container, it uses "docker kill" as opposed to "docker \
stop".   I can see the reasoning behind this, but it causes a problem in that the \
container doesn't get a  chance to clean up after itself.   </div>
<div><br>
</div>
<div>Is this something that might be addressed?   Perhaps by trying docker stop and \
then running kill if it doesn't shut down after 30 seconds or something?   </div> \
<div><br> </div>
<div>Thanks,</div>
<div>Scott</div>
<p><font size="-2">This email message contains information that Corporate \
Reimbursement Services, Inc. considers confidential and/or proprietary, or may later \
designate as confidential and proprietary. It is intended only for use of the \
individual or entity  named above and should not be forwarded to any other persons or \
entities without the express consent of Corporate Reimbursement Services, Inc., nor \
should it be used for any purpose other than in the course of any potential or actual \
business relationship  with Corporate Reimbursement Services, Inc. If the reader of \
this message is not the intended recipient, or the employee or agent responsible to \
deliver it to the intended recipient, you are hereby notified that any dissemination, \
distribution, or copying  of this communication is strictly prohibited. If you have \
received this communication in error, please notify sender immediately and destroy \
the original message.</font></p> <p><font size="-2">Internal Revenue Service \
regulations require that certain types of written advice include a disclaimer. To the \
extent the preceding message contains advice relating to a Federal tax issue, unless \
expressly stated otherwise the advice is not  intended or written to be used, and it \
cannot be used by the recipient or any other taxpayer, for the purpose of avoiding \
Federal tax penalties, and was not written to support the promotion or marketing of \
any transaction or matter discussed herein.</font></p> </div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</span>
<p><font size="-2">This email message contains information that Corporate \
Reimbursement Services, Inc. considers confidential and/or proprietary, or may later \
designate as confidential and proprietary. It is intended only for use of the \
individual or entity  named above and should not be forwarded to any other persons or \
entities without the express consent of Corporate Reimbursement Services, Inc., nor \
should it be used for any purpose other than in the course of any potential or actual \
business relationship  with Corporate Reimbursement Services, Inc. If the reader of \
this message is not the intended recipient, or the employee or agent responsible to \
deliver it to the intended recipient, you are hereby notified that any dissemination, \
distribution, or copying  of this communication is strictly prohibited. If you have \
received this communication in error, please notify sender immediately and destroy \
the original message.</font></p> <p><font size="-2">Internal Revenue Service \
regulations require that certain types of written advice include a disclaimer. To the \
extent the preceding message contains advice relating to a Federal tax issue, unless \
expressly stated otherwise the advice is not  intended or written to be used, and it \
cannot be used by the recipient or any other taxpayer, for the purpose of avoiding \
Federal tax penalties, and was not written to support the promotion or marketing of \
any transaction or matter discussed herein.</font></p> </div>

</blockquote></div>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic