Mailing-List: contact user-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@mesos.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
From: Ankur Chauhan <ankur@malloc64.com>
Content-Type: multipart/alternative;
	boundary=Apple-Mail-DBEDE6B0-B8F5-4E11-9931-50538228D461
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Subject: Re: Killing Docker containers
Message-Id: <9614BA5A-3FE4-4743-B3D4-CDF241E845C5@malloc64.com>
Date: Tue, 14 Oct 2014 14:32:16 -0700
References: <D062E4EB.4A7A5%srankin@crsinc.com>
 <CANbyX1X-r4fomj0wyN_CNVAB2ZdpMQPRU51JGGaaF3FbLyWicQ@mail.gmail.com>
In-Reply-To: 
 <CANbyX1X-r4fomj0wyN_CNVAB2ZdpMQPRU51JGGaaF3FbLyWicQ@mail.gmail.com>
To: "user@mesos.apache.org" <user@mesos.apache.org>


--Apple-Mail-DBEDE6B0-B8F5-4E11-9931-50538228D461
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

++ I was planning on submitting that patch. But if someone has this sorted o=
ut already, I'll defer.=20

Sent from my iPhone

> On Oct 14, 2014, at 2:19 PM, Ryan Thomas <r.n.thomas@gmail.com> wrote:
>=20
> The docker stop command will attempt to kill the container if it doesn't s=
top in 10 seconds by default. I think we should be using this with the -t fl=
ag to control the time between stop and kill rather than just using kill.
>=20
> I'll try to submit a patch.
>=20
> Cheers,
>=20
> ryan
>=20
>> On 15 October 2014 05:37, Scott Rankin <srankin@crsinc.com> wrote:
>> Hi All,
>>=20
>> I=E2=80=99m working on prototyping Mesos+Marathon for our services platfo=
rm, using apps deployed as Docker containers.  Our applications register the=
mselves with our service discovery framework on startup and un-register them=
selves when they shut down (assuming they shut down reasonably gracefully). =
 What I=E2=80=99m finding is that when Mesos shuts down a docker container, i=
t uses =E2=80=9Cdocker kill=E2=80=9D as opposed to =E2=80=9Cdocker stop=E2=80=
=9D.  I can see the reasoning behind this, but it causes a problem in that t=
he container doesn=E2=80=99t get a chance to clean up after itself. =20
>>=20
>> Is this something that might be addressed?  Perhaps by trying docker stop=
 and then running kill if it doesn=E2=80=99t shut down after 30 seconds or s=
omething? =20
>>=20
>> Thanks,
>> Scott
>> This email message contains information that Corporate Reimbursement Serv=
ices, Inc. considers confidential and/or proprietary, or may later designate=
 as confidential and proprietary. It is intended only for use of the individ=
ual or entity named above and should not be forwarded to any other persons o=
r entities without the express consent of Corporate Reimbursement Services, I=
nc., nor should it be used for any purpose other than in the course of any p=
otential or actual business relationship with Corporate Reimbursement Servic=
es, 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 a=
re hereby notified that any dissemination, distribution, or copying of this c=
ommunication is strictly prohibited. If you have received this communication=
 in error, please notify sender immediately and destroy the original message=
.
>>=20
>> Internal Revenue Service regulations require that certain types of writte=
n advice include a disclaimer. To the extent the preceding message contains a=
dvice 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 r=
ecipient or any other taxpayer, for the purpose of avoiding Federal tax pena=
lties, and was not written to support the promotion or marketing of any tran=
saction or matter discussed herein.
>>=20
>=20

--Apple-Mail-DBEDE6B0-B8F5-4E11-9931-50538228D461
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>++ I was planning on submitting that p=
atch. But if someone has this sorted out already, I'll defer.&nbsp;<br><br>S=
ent from my iPhone</div><div><br>On Oct 14, 2014, at 2:19 PM, Ryan Thomas &l=
t;<a href=3D"mailto:r.n.thomas@gmail.com">r.n.thomas@gmail.com</a>&gt; wrote=
:<br><br></div><blockquote type=3D"cite"><div><div dir=3D"ltr">The docker st=
op command will attempt to kill the container if it doesn't stop in 10 secon=
ds by default. I think we should be using this with the -t flag to control t=
he time between stop and kill rather than just using kill.<div><br></div><di=
v>I'll try to submit a patch.</div><div><br></div><div>Cheers,</div><div><br=
></div><div>ryan</div></div><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On 15 October 2014 05:37, Scott Rankin <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:srankin@crsinc.com" target=3D"_blank">srankin@crsinc.com</a>&gt=
;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">


<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-fami=
ly:Calibri,sans-serif">
<div>Hi All,</div>
<div><br>
</div>
<div>I=E2=80=99m working on prototyping Mesos+Marathon for our services plat=
form, using apps deployed as Docker containers.&nbsp; Our applications regis=
ter themselves with our service discovery framework on startup and un-regist=
er themselves when they shut down (assuming
 they shut down reasonably gracefully).&nbsp; What I=E2=80=99m finding is th=
at when Mesos shuts down a docker container, it uses =E2=80=9Cdocker kill=E2=
=80=9D as opposed to =E2=80=9Cdocker stop=E2=80=9D.&nbsp; I can see the reas=
oning behind this, but it causes a problem in that the container doesn=E2=80=
=99t get a
 chance to clean up after itself. &nbsp;</div>
<div><br>
</div>
<div>Is this something that might be addressed?&nbsp; Perhaps by trying dock=
er stop and then running kill if it doesn=E2=80=99t shut down after 30 secon=
ds or something? &nbsp;</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Scott</div>
<p><font size=3D"-2">This email message contains information that Corporate R=
eimbursement Services, Inc. considers confidential and/or proprietary, or ma=
y later designate as confidential and proprietary. It is intended only for u=
se of the individual or entity
 named above and should not be forwarded to any other persons or entities wi=
thout the express consent of Corporate Reimbursement Services, Inc., nor sho=
uld it be used for any purpose other than in the course of any potential or a=
ctual business relationship
 with Corporate Reimbursement Services, Inc. If the reader of this message i=
s not the intended recipient, or the employee or agent responsible to delive=
r it to the intended recipient, you are hereby notified that any disseminati=
on, distribution, or copying
 of this communication is strictly prohibited. If you have received this com=
munication in error, please notify sender immediately and destroy the origin=
al message.</font></p>
<p><font size=3D"-2">Internal Revenue Service regulations require that certa=
in types of written advice include a disclaimer. To the extent the preceding=
 message contains advice relating to a Federal tax issue, unless expressly s=
tated otherwise the advice is not
 intended or written to be used, and it cannot be used by the recipient or a=
ny other taxpayer, for the purpose of avoiding Federal tax penalties, and wa=
s not written to support the promotion or marketing of any transaction or ma=
tter discussed herein.</font></p>
</div>

</blockquote></div><br></div>
</div></blockquote></body></html>=

--Apple-Mail-DBEDE6B0-B8F5-4E11-9931-50538228D461--