You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by nirmalendu swain <ni...@yahoo.com> on 2016/04/12 08:13:02 UTC
marathon issue in running a docker container.
Hi Mesos user,I am running mesos marathon using dcos for spinning up AWS instances. I have successfully built the mongodb as a docker container, but when I try to deploy my dockerized app, it does n't deploy. My App is dependent upon mongo which is passed as environment variable in the json file to be run by dcos command. If a i do a telnet/curl, it does n't receive at the desired host:port. from the mesos logs, it does not seem to throw any error/exception. Doing a copy-past of my backend-app.json file which falis to deploy.
{ "id": "/todo-with-backend", "instances": 2, "container": { "type": "DOCKER", "docker": { "image": "tldr/todo-backend", "network": "BRIDGE", "portMappings": [ { "containerPort": 8080, "hostPort": 0, "protocol": "tcp" } ] } }, "env":{ "MONGO_URL":"10.0.2.252:5530" }, "healthChecks": [{ "protocol": "HTTP", "portIndex": 0 }], "labels":{ "HAPROXY_GROUP":"external", "<Using the same ELB as that of mongo json file>" }, "cpus": 0.25, "mem": 256.0}
I have gone inside the host and checked that env value is reflecting correctly.Please help me out in analyzing the issue.
Regards,Nirmal
Re: marathon issue in running a docker container.
Posted by nirmalendu swain <ni...@yahoo.com>.
When marathon launches the task while network : "BRIDGE", I can see from the mesos log that its listening to some host:port Even I can do an ssh to that instance, also saw MONGO_URL as env value over there. Pasting the log below --
--container="mesos-87849fd2-fda9-4d6a-870f-de101a5bdc59-S1.864e0bbb-02b5-4634-a6e5-a840993d181d" --docker="docker" --docker_socket="/var/run/docker.sock" --help="false" --initialize_driver_logging="true" --launcher_dir="/opt/mesosphere/packages/mesos--b012cc908778011b3c6b09b1ebaa06f5e0a93ccd/libexec/mesos" --logbufsecs="0" --logging_level="INFO" --mapped_directory="/mnt/mesos/sandbox" --quiet="false" --sandbox_directory="/var/lib/mesos/slave/slaves/87849fd2-fda9-4d6a-870f-de101a5bdc59-S1/frameworks/87849fd2-fda9-4d6a-870f-de101a5bdc59-0000/executors/todo-with-backend.031a8d1c-fd79-11e5-afa9-024212f8e488/runs/864e0bbb-02b5-4634-a6e5-a840993d181d" --stop_timeout="0ns"--container="mesos-87849fd2-fda9-4d6a-870f-de101a5bdc59-S1.864e0bbb-02b5-4634-a6e5-a840993d181d" --docker="docker" --docker_socket="/var/run/docker.sock" --help="false" --initialize_driver_logging="true" --launcher_dir="/opt/mesosphere/packages/mesos--b012cc908778011b3c6b09b1ebaa06f5e0a93ccd/libexec/mesos" --logbufsecs="0" --logging_level="INFO" --mapped_directory="/mnt/mesos/sandbox" --quiet="false" --sandbox_directory="/var/lib/mesos/slave/slaves/87849fd2-fda9-4d6a-870f-de101a5bdc59-S1/frameworks/87849fd2-fda9-4d6a-870f-de101a5bdc59-0000/executors/todo-with-backend.031a8d1c-fd79-11e5-afa9-024212f8e488/runs/864e0bbb-02b5-4634-a6e5-a840993d181d" --stop_timeout="0ns"Registered docker executor on 10.0.2.253Starting task todo-with-backend.031a8d1c-fd79-11e5-afa9-024212f8e488Waiting for Mongo to become available. Will try for 60 seconds.Starting service.{ [Error: Cannot find module '../build/Release/bson'] code: 'MODULE_NOT_FOUND' }[33m################################################################ !!! MONGOOSE WARNING !!!## This is an UNSTABLE release of Mongoose.# Unstable releases are available for preview/testing only.# DO NOT run this in production.###############################################################[0mServer running at: http://0.0.0.0:7683
On Tuesday, 12 April 2016 1:35 PM, haosdent <ha...@gmail.com> wrote:
>Its frequently changing the deployment status to Staged
Do you find any related log in mesos when marathon lauch the task?
On Tue, Apr 12, 2016 at 3:55 PM, nirmalendu swain <ni...@yahoo.com> wrote:
Changing the network type to HOST does not work. Its frequently changing the deployment status to Staged and then to no task.
On Tuesday, 12 April 2016 11:49 AM, haosdent <ha...@gmail.com> wrote:
How about change the network type from BRIDGE to HOST?
On Tue, Apr 12, 2016 at 2:13 PM, nirmalendu swain <ni...@yahoo.com> wrote:
Hi Mesos user,I am running mesos marathon using dcos for spinning up AWS instances. I have successfully built the mongodb as a docker container, but when I try to deploy my dockerized app, it does n't deploy. My App is dependent upon mongo which is passed as environment variable in the json file to be run by dcos command. If a i do a telnet/curl, it does n't receive at the desired host:port. from the mesos logs, it does not seem to throw any error/exception. Doing a copy-past of my backend-app.json file which falis to deploy.
{ "id": "/todo-with-backend", "instances": 2, "container": { "type": "DOCKER", "docker": { "image": "tldr/todo-backend", "network": "BRIDGE", "portMappings": [ { "containerPort": 8080, "hostPort": 0, "protocol": "tcp" } ] } }, "env":{ "MONGO_URL":"10.0.2.252:5530" }, "healthChecks": [{ "protocol": "HTTP", "portIndex": 0 }], "labels":{ "HAPROXY_GROUP":"external", "<Using the same ELB as that of mongo json file>" }, "cpus": 0.25, "mem": 256.0}
I have gone inside the host and checked that env value is reflecting correctly.Please help me out in analyzing the issue.
Regards,Nirmal
--
Best Regards,
Haosdent Huang
--
Best Regards,
Haosdent Huang
Re: marathon issue in running a docker container.
Posted by haosdent <ha...@gmail.com>.
>Its frequently changing the deployment status to Staged
Do you find any related log in mesos when marathon lauch the task?
On Tue, Apr 12, 2016 at 3:55 PM, nirmalendu swain <
nirmalendu_swain@yahoo.com> wrote:
> Changing the network type to HOST does not work. Its frequently changing
> the deployment status to Staged and then to no task.
>
>
> On Tuesday, 12 April 2016 11:49 AM, haosdent <ha...@gmail.com> wrote:
>
>
> How about change the network type from BRIDGE to HOST?
>
> On Tue, Apr 12, 2016 at 2:13 PM, nirmalendu swain <
> nirmalendu_swain@yahoo.com> wrote:
>
> Hi Mesos user,
> I am running mesos marathon using dcos for spinning up AWS instances.
> I have successfully built the mongodb as a docker container, but when I
> try to deploy my dockerized app, it does n't deploy. My App is dependent
> upon mongo which is passed as environment variable in the json file to be
> run by dcos command. If a i do a telnet/curl, it does n't receive at the
> desired host:port. from the mesos logs, it does not seem to throw any
> error/exception. Doing a copy-past of my backend-app.json file which falis
> to deploy.
>
>
> *{*
> * "id": "/todo-with-backend",*
> * "instances": 2,*
> * "container": {*
> * "type": "DOCKER",*
> * "docker": {*
> * "image": "tldr/todo-backend",*
> * "network": "BRIDGE",*
> * "portMappings": [*
> * {*
> * "containerPort": 8080,*
> * "hostPort": 0,*
> * "protocol": "tcp"*
> * }*
> * ]*
> * }*
> * },*
> * "env":{*
> * "MONGO_URL":"10.0.2.252:5530 <http://10.0.2.252:5530/>"*
> * },*
> * "healthChecks": [{*
> * "protocol": "HTTP",*
> * "portIndex": 0*
> * }],*
> * "labels":{*
> * "HAPROXY_GROUP":"external",*
> * "<Using the same ELB as that of mongo json file>"*
> * },*
> * "cpus": 0.25,*
> * "mem": 256.0*
> *}*
>
> I have gone inside the host and checked that env value is reflecting
> correctly.
> Please help me out in analyzing the issue.
>
> Regards,
> Nirmal
>
>
>
>
>
> --
> Best Regards,
> Haosdent Huang
>
>
>
--
Best Regards,
Haosdent Huang
Re: marathon issue in running a docker container.
Posted by nirmalendu swain <ni...@yahoo.com>.
Changing the network type to HOST does not work. Its frequently changing the deployment status to Staged and then to no task.
On Tuesday, 12 April 2016 11:49 AM, haosdent <ha...@gmail.com> wrote:
How about change the network type from BRIDGE to HOST?
On Tue, Apr 12, 2016 at 2:13 PM, nirmalendu swain <ni...@yahoo.com> wrote:
Hi Mesos user,I am running mesos marathon using dcos for spinning up AWS instances. I have successfully built the mongodb as a docker container, but when I try to deploy my dockerized app, it does n't deploy. My App is dependent upon mongo which is passed as environment variable in the json file to be run by dcos command. If a i do a telnet/curl, it does n't receive at the desired host:port. from the mesos logs, it does not seem to throw any error/exception. Doing a copy-past of my backend-app.json file which falis to deploy.
{ "id": "/todo-with-backend", "instances": 2, "container": { "type": "DOCKER", "docker": { "image": "tldr/todo-backend", "network": "BRIDGE", "portMappings": [ { "containerPort": 8080, "hostPort": 0, "protocol": "tcp" } ] } }, "env":{ "MONGO_URL":"10.0.2.252:5530" }, "healthChecks": [{ "protocol": "HTTP", "portIndex": 0 }], "labels":{ "HAPROXY_GROUP":"external", "<Using the same ELB as that of mongo json file>" }, "cpus": 0.25, "mem": 256.0}
I have gone inside the host and checked that env value is reflecting correctly.Please help me out in analyzing the issue.
Regards,Nirmal
--
Best Regards,
Haosdent Huang
Re: marathon issue in running a docker container.
Posted by haosdent <ha...@gmail.com>.
How about change the network type from BRIDGE to HOST?
On Tue, Apr 12, 2016 at 2:13 PM, nirmalendu swain <
nirmalendu_swain@yahoo.com> wrote:
> Hi Mesos user,
> I am running mesos marathon using dcos for spinning up AWS instances.
> I have successfully built the mongodb as a docker container, but when I
> try to deploy my dockerized app, it does n't deploy. My App is dependent
> upon mongo which is passed as environment variable in the json file to be
> run by dcos command. If a i do a telnet/curl, it does n't receive at the
> desired host:port. from the mesos logs, it does not seem to throw any
> error/exception. Doing a copy-past of my backend-app.json file which falis
> to deploy.
>
>
> *{*
> * "id": "/todo-with-backend",*
> * "instances": 2,*
> * "container": {*
> * "type": "DOCKER",*
> * "docker": {*
> * "image": "tldr/todo-backend",*
> * "network": "BRIDGE",*
> * "portMappings": [*
> * {*
> * "containerPort": 8080,*
> * "hostPort": 0,*
> * "protocol": "tcp"*
> * }*
> * ]*
> * }*
> * },*
> * "env":{*
> * "MONGO_URL":"10.0.2.252:5530 <http://10.0.2.252:5530>"*
> * },*
> * "healthChecks": [{*
> * "protocol": "HTTP",*
> * "portIndex": 0*
> * }],*
> * "labels":{*
> * "HAPROXY_GROUP":"external",*
> * "<Using the same ELB as that of mongo json file>"*
> * },*
> * "cpus": 0.25,*
> * "mem": 256.0*
> *}*
>
> I have gone inside the host and checked that env value is reflecting
> correctly.
> Please help me out in analyzing the issue.
>
> Regards,
> Nirmal
>
>
>
--
Best Regards,
Haosdent Huang