You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by ai...@accenture.com on 2016/04/21 12:18:26 UTC
Marathon Docker Application Deployment Issue
Hi ,
I have setup single mesos master and single slave machine in my environment. And trying to run Docker container on mesos slave.
I am able to run the application in CLI but unable to deploy using Marathon GUI.I am trying to deploy hello-world image.
It keeps showing up status as waiting under deployment.
I don't know why is it taking so much of time as hello world is a small image it should not take much time.
Can you please help me with this.
Thank you
________________________________
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.
______________________________________________________________________________________
www.accenture.com
Re: Marathon Docker Application Deployment Issue
Posted by Shuai Lin <li...@gmail.com>.
IIRC there is an option that can force pull a image when launching a task,
even if the image is already there. Can you paste the request you sent to
marathon?
On Fri, Apr 22, 2016 at 11:19 AM, <ai...@accenture.com>
wrote:
> Hi,
>
>
>
> I have pulled the docker image on to my slave machine and haven’t used a
> docker hub instead.
>
>
>
> *From:* Shuai Lin [mailto:linshuai2012@gmail.com]
> *Sent:* 21 April 2016 18:34
>
> *To:* user <us...@mesos.apache.org>
> *Subject:* Re: Marathon Docker Application Deployment Issue
>
>
>
> As you can see from the slave log, the docker daemon on your mesos slave
> failed to pull the image, because it can't connect to docker hub.
>
>
>
> On Thu, Apr 21, 2016 at 7:30 PM, <ai...@accenture.com>
> wrote:
>
> Hi,
>
>
>
> This is what is being seen in the file mesos-slave.ERROR:
>
>
>
> E0421 03:01:38.740025 2797 slave.cpp:3703] Container
> 'de0c5a4b-0041-4684-9f63-659094046a9e' for executor
> 'python-app.4883b6ab-076d-11e6-8f06-02423a6b81f2' of framework
> 687c0248-cfc6-4710-80c3-fd302da3a6ba-0000 failed to start: Failed to
> 'docker -H unix:///var/run/docker.sock pull python:3': exit status = exited
> with status 1 stderr = Network timed out while trying to connect to
> https://index.docker.io/v1/repositories/library/python/images. You may
> want to check your internet connection or if you are behind a proxy.
>
> E0421 03:02:18.786658 2797 slave.cpp:3703] Container
> '3b6d9d6c-9771-4905-802e-a380cb14724c' for executor
> 'python-app.60696b7e-076d-11e6-8f06-02423a6b81f2' of framework
> 687c0248-cfc6-4710-80c3-fd302da3a6ba-0000 failed to start: Failed to
> 'docker -H unix:///var/run/docker.sock pull python:3': exit status = exited
> with status 1 stderr = Network timed out while trying to connect to
> https://index.docker.io/v1/repositories/library/python/images. You may
> want to check your internet connection or if you are behind a proxy.
>
> E0421 03:02:18.789577 2799 slave.cpp:3703] Container
> 'e8594886-9e64-4a9c-a0c2-58f73303da3d' for executor
> 'python-app.6068f64d-076d-11e6-8f06-02423a6b81f2' of framework
> 687c0248-cfc6-4710-80c3-fd302da3a6ba-0000 failed to start: Failed to
> 'docker -H unix:///var/run/docker.sock pull python:3': exit status = exited
> with status 1 stderr = Network timed out while trying to connect to
> https://index.docker.io/v1/repositories/library/python/images. You may
> want to check your internet connection or if you are behind a proxy.
>
> E0421 03:02:21.453006 2804 process.cpp:1966] Failed to shutdown socket
> with fd 9: Transport endpoint is not connected
>
> E0421 03:02:22.856468 2804 process.cpp:1966] Failed to shutdown socket
> with fd 9: Transport endpoint is not connected
>
>
>
> Thank you.
>
>
>
> *From:* Shuai Lin [mailto:linshuai2012@gmail.com]
> *Sent:* 21 April 2016 15:54
> *To:* user <us...@mesos.apache.org>
> *Subject:* Re: Marathon Docker Application Deployment Issue
>
>
>
> There should be detailed error messages somewhere. Check your mesos slave
> logs, marathon logs, and docker daemon logs.
>
>
>
> On Thu, Apr 21, 2016 at 6:18 PM, <ai...@accenture.com>
> wrote:
>
> Hi ,
>
>
>
> I have setup single mesos master and single slave machine in my
> environment. And trying to run Docker container on mesos slave.
>
> I am able to run the application in CLI but unable to deploy using
> Marathon GUI.I am trying to deploy hello-world image.
>
>
>
> It keeps showing up status as waiting under deployment.
>
> I don’t know why is it taking so much of time as hello world is a small
> image it should not take much time.
>
>
>
> Can you please help me with this.
>
>
>
> Thank you
>
>
>
>
>
>
>
>
>
>
>
>
> ------------------------------
>
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise confidential information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the e-mail by you is prohibited. Where allowed
> by local law, electronic communications with Accenture and its affiliates,
> including e-mail and instant messaging (including content), may be scanned
> by our systems for the purposes of information security and assessment of
> internal compliance with Accenture policy.
>
> ______________________________________________________________________________________
>
> www.accenture.com
>
>
>
>
>
RE: Marathon Docker Application Deployment Issue
Posted by ai...@accenture.com.
Hi,
I have pulled the docker image on to my slave machine and haven’t used a docker hub instead.
From: Shuai Lin [mailto:linshuai2012@gmail.com]
Sent: 21 April 2016 18:34
To: user <us...@mesos.apache.org>
Subject: Re: Marathon Docker Application Deployment Issue
As you can see from the slave log, the docker daemon on your mesos slave failed to pull the image, because it can't connect to docker hub.
On Thu, Apr 21, 2016 at 7:30 PM, <ai...@accenture.com>> wrote:
Hi,
This is what is being seen in the file mesos-slave.ERROR:
E0421 03:01:38.740025 2797 slave.cpp:3703] Container 'de0c5a4b-0041-4684-9f63-659094046a9e' for executor 'python-app.4883b6ab-076d-11e6-8f06-02423a6b81f2' of framework 687c0248-cfc6-4710-80c3-fd302da3a6ba-0000 failed to start: Failed to 'docker -H unix:///var/run/docker.sock pull python:3': exit status = exited with status 1 stderr = Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/python/images. You may want to check your internet connection or if you are behind a proxy.
E0421 03:02:18.786658 2797 slave.cpp:3703] Container '3b6d9d6c-9771-4905-802e-a380cb14724c' for executor 'python-app.60696b7e-076d-11e6-8f06-02423a6b81f2' of framework 687c0248-cfc6-4710-80c3-fd302da3a6ba-0000 failed to start: Failed to 'docker -H unix:///var/run/docker.sock pull python:3': exit status = exited with status 1 stderr = Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/python/images. You may want to check your internet connection or if you are behind a proxy.
E0421 03:02:18.789577 2799 slave.cpp:3703] Container 'e8594886-9e64-4a9c-a0c2-58f73303da3d' for executor 'python-app.6068f64d-076d-11e6-8f06-02423a6b81f2' of framework 687c0248-cfc6-4710-80c3-fd302da3a6ba-0000 failed to start: Failed to 'docker -H unix:///var/run/docker.sock pull python:3': exit status = exited with status 1 stderr = Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/python/images. You may want to check your internet connection or if you are behind a proxy.
E0421 03:02:21.453006 2804 process.cpp:1966] Failed to shutdown socket with fd 9: Transport endpoint is not connected
E0421 03:02:22.856468 2804 process.cpp:1966] Failed to shutdown socket with fd 9: Transport endpoint is not connected
Thank you.
From: Shuai Lin [mailto:linshuai2012@gmail.com<ma...@gmail.com>]
Sent: 21 April 2016 15:54
To: user <us...@mesos.apache.org>>
Subject: Re: Marathon Docker Application Deployment Issue
There should be detailed error messages somewhere. Check your mesos slave logs, marathon logs, and docker daemon logs.
On Thu, Apr 21, 2016 at 6:18 PM, <ai...@accenture.com>> wrote:
Hi ,
I have setup single mesos master and single slave machine in my environment. And trying to run Docker container on mesos slave.
I am able to run the application in CLI but unable to deploy using Marathon GUI.I am trying to deploy hello-world image.
It keeps showing up status as waiting under deployment.
I don’t know why is it taking so much of time as hello world is a small image it should not take much time.
Can you please help me with this.
Thank you
________________________________
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.
______________________________________________________________________________________
www.accenture.com<http://www.accenture.com>
Re: Marathon Docker Application Deployment Issue
Posted by Shuai Lin <li...@gmail.com>.
As you can see from the slave log, the docker daemon on your mesos slave
failed to pull the image, because it can't connect to docker hub.
On Thu, Apr 21, 2016 at 7:30 PM, <ai...@accenture.com> wrote:
> Hi,
>
>
>
> This is what is being seen in the file mesos-slave.ERROR:
>
>
>
> E0421 03:01:38.740025 2797 slave.cpp:3703] Container
> 'de0c5a4b-0041-4684-9f63-659094046a9e' for executor
> 'python-app.4883b6ab-076d-11e6-8f06-02423a6b81f2' of framework
> 687c0248-cfc6-4710-80c3-fd302da3a6ba-0000 failed to start: Failed to
> 'docker -H unix:///var/run/docker.sock pull python:3': exit status = exited
> with status 1 stderr = Network timed out while trying to connect to
> https://index.docker.io/v1/repositories/library/python/images. You may
> want to check your internet connection or if you are behind a proxy.
>
> E0421 03:02:18.786658 2797 slave.cpp:3703] Container
> '3b6d9d6c-9771-4905-802e-a380cb14724c' for executor
> 'python-app.60696b7e-076d-11e6-8f06-02423a6b81f2' of framework
> 687c0248-cfc6-4710-80c3-fd302da3a6ba-0000 failed to start: Failed to
> 'docker -H unix:///var/run/docker.sock pull python:3': exit status = exited
> with status 1 stderr = Network timed out while trying to connect to
> https://index.docker.io/v1/repositories/library/python/images. You may
> want to check your internet connection or if you are behind a proxy.
>
> E0421 03:02:18.789577 2799 slave.cpp:3703] Container
> 'e8594886-9e64-4a9c-a0c2-58f73303da3d' for executor
> 'python-app.6068f64d-076d-11e6-8f06-02423a6b81f2' of framework
> 687c0248-cfc6-4710-80c3-fd302da3a6ba-0000 failed to start: Failed to
> 'docker -H unix:///var/run/docker.sock pull python:3': exit status = exited
> with status 1 stderr = Network timed out while trying to connect to
> https://index.docker.io/v1/repositories/library/python/images. You may
> want to check your internet connection or if you are behind a proxy.
>
> E0421 03:02:21.453006 2804 process.cpp:1966] Failed to shutdown socket
> with fd 9: Transport endpoint is not connected
>
> E0421 03:02:22.856468 2804 process.cpp:1966] Failed to shutdown socket
> with fd 9: Transport endpoint is not connected
>
>
>
> Thank you.
>
>
>
> *From:* Shuai Lin [mailto:linshuai2012@gmail.com]
> *Sent:* 21 April 2016 15:54
> *To:* user <us...@mesos.apache.org>
> *Subject:* Re: Marathon Docker Application Deployment Issue
>
>
>
> There should be detailed error messages somewhere. Check your mesos slave
> logs, marathon logs, and docker daemon logs.
>
>
>
> On Thu, Apr 21, 2016 at 6:18 PM, <ai...@accenture.com>
> wrote:
>
> Hi ,
>
>
>
> I have setup single mesos master and single slave machine in my
> environment. And trying to run Docker container on mesos slave.
>
> I am able to run the application in CLI but unable to deploy using
> Marathon GUI.I am trying to deploy hello-world image.
>
>
>
> It keeps showing up status as waiting under deployment.
>
> I don’t know why is it taking so much of time as hello world is a small
> image it should not take much time.
>
>
>
> Can you please help me with this.
>
>
>
> Thank you
>
>
>
>
>
>
>
>
>
>
>
>
> ------------------------------
>
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise confidential information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the e-mail by you is prohibited. Where allowed
> by local law, electronic communications with Accenture and its affiliates,
> including e-mail and instant messaging (including content), may be scanned
> by our systems for the purposes of information security and assessment of
> internal compliance with Accenture policy.
>
> ______________________________________________________________________________________
>
> www.accenture.com
>
>
>
RE: Marathon Docker Application Deployment Issue
Posted by ai...@accenture.com.
Hi,
This is what is being seen in the file mesos-slave.ERROR:
E0421 03:01:38.740025 2797 slave.cpp:3703] Container 'de0c5a4b-0041-4684-9f63-659094046a9e' for executor 'python-app.4883b6ab-076d-11e6-8f06-02423a6b81f2' of framework 687c0248-cfc6-4710-80c3-fd302da3a6ba-0000 failed to start: Failed to 'docker -H unix:///var/run/docker.sock pull python:3': exit status = exited with status 1 stderr = Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/python/images. You may want to check your internet connection or if you are behind a proxy.
E0421 03:02:18.786658 2797 slave.cpp:3703] Container '3b6d9d6c-9771-4905-802e-a380cb14724c' for executor 'python-app.60696b7e-076d-11e6-8f06-02423a6b81f2' of framework 687c0248-cfc6-4710-80c3-fd302da3a6ba-0000 failed to start: Failed to 'docker -H unix:///var/run/docker.sock pull python:3': exit status = exited with status 1 stderr = Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/python/images. You may want to check your internet connection or if you are behind a proxy.
E0421 03:02:18.789577 2799 slave.cpp:3703] Container 'e8594886-9e64-4a9c-a0c2-58f73303da3d' for executor 'python-app.6068f64d-076d-11e6-8f06-02423a6b81f2' of framework 687c0248-cfc6-4710-80c3-fd302da3a6ba-0000 failed to start: Failed to 'docker -H unix:///var/run/docker.sock pull python:3': exit status = exited with status 1 stderr = Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/python/images. You may want to check your internet connection or if you are behind a proxy.
E0421 03:02:21.453006 2804 process.cpp:1966] Failed to shutdown socket with fd 9: Transport endpoint is not connected
E0421 03:02:22.856468 2804 process.cpp:1966] Failed to shutdown socket with fd 9: Transport endpoint is not connected
Thank you.
From: Shuai Lin [mailto:linshuai2012@gmail.com]
Sent: 21 April 2016 15:54
To: user <us...@mesos.apache.org>
Subject: Re: Marathon Docker Application Deployment Issue
There should be detailed error messages somewhere. Check your mesos slave logs, marathon logs, and docker daemon logs.
On Thu, Apr 21, 2016 at 6:18 PM, <ai...@accenture.com>> wrote:
Hi ,
I have setup single mesos master and single slave machine in my environment. And trying to run Docker container on mesos slave.
I am able to run the application in CLI but unable to deploy using Marathon GUI.I am trying to deploy hello-world image.
It keeps showing up status as waiting under deployment.
I don’t know why is it taking so much of time as hello world is a small image it should not take much time.
Can you please help me with this.
Thank you
________________________________
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.
______________________________________________________________________________________
www.accenture.com<http://www.accenture.com>
Re: Marathon Docker Application Deployment Issue
Posted by Shuai Lin <li...@gmail.com>.
There should be detailed error messages somewhere. Check your mesos slave
logs, marathon logs, and docker daemon logs.
On Thu, Apr 21, 2016 at 6:18 PM, <ai...@accenture.com> wrote:
> Hi ,
>
>
>
> I have setup single mesos master and single slave machine in my
> environment. And trying to run Docker container on mesos slave.
>
> I am able to run the application in CLI but unable to deploy using
> Marathon GUI.I am trying to deploy hello-world image.
>
>
>
> It keeps showing up status as waiting under deployment.
>
> I don’t know why is it taking so much of time as hello world is a small
> image it should not take much time.
>
>
>
> Can you please help me with this.
>
>
>
> Thank you
>
>
>
>
>
>
>
>
>
>
>
> ------------------------------
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise confidential information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the e-mail by you is prohibited. Where allowed
> by local law, electronic communications with Accenture and its affiliates,
> including e-mail and instant messaging (including content), may be scanned
> by our systems for the purposes of information security and assessment of
> internal compliance with Accenture policy.
>
> ______________________________________________________________________________________
>
> www.accenture.com
>