unable to access helloworld App deployed using DCOS Marathon in Azure

Question

I have deployed a hello world application in Azure using DCOS and Marathon Framework.I am trying to access that using fqn: portnumber at which the application is hosted. I am unable to open the application

Following is the json I have used

{
  "id": "/dockercloud-hello-world",
  "cmd": null,
  "cpus": 0.1,
  "mem": 128,
  "disk": 0,
  "instances": 2,
  "acceptedResourceRoles": [
    "*"
  ],
  "container": {
    "type": "DOCKER",
    "volumes": [],
    "docker": {
      "image": "dockercloud/hello-world",
      "network": "BRIDGE",
      "portMappings": [
        {
          "containerPort": 80,
          "hostPort": 0,
          "servicePort": 10000,
          "protocol": "tcp",
          "labels": {}
        }
      ],
      "privileged": false,
      "parameters": [],
      "forcePullImage": true
    }
  },
  "healthChecks": [
    {
      "gracePeriodSeconds": 10,
      "intervalSeconds": 2,
      "timeoutSeconds": 10,
      "maxConsecutiveFailures": 10,
      "portIndex": 0,
      "path": "/",
      "protocol": "HTTP",
      "ignoreHttp1xx": false
    }
  ],
  "portDefinitions": [
    {
      "port": 10000,
      "protocol": "tcp",
      "name": "default",
      "labels": {}
    }
  ]
}

I have added NSG Inbound rule for master nsg resource I have added NAT rule for master lb resource allowing the port as custom

score 1 · Accepted Answer · answered Mar 01 '18 at 05:44

1

In your example, host port is 0, Azure will listen your service on a random port. You need open the port on NSG and lb.

I suggest you could specify the port, you could check the following example:

{
  "id": "/dockercloud-hello-world",
  "cmd": null,
  "cpus": 0.1,
  "mem": 32,
  "disk": 0,
  "instances": 1,
  "acceptedResourceRoles": [
    "slave_public"
  ],
  "container": {
    "type": "DOCKER",
    "volumes": [],
    "docker": {
      "image": "dockercloud/hello-world",
      "network": "BRIDGE",
      "portMappings": [
        {
          "containerPort": 80,
          "hostPort": 80,
          "protocol": "tcp",
          "labels": {},
          "name": "test80"
        }
      ],
      "privileged": false,
      "parameters": [],
      "forcePullImage": true
    }
  },
  "healthChecks": [
    {
      "gracePeriodSeconds": 10,
      "intervalSeconds": 2,
      "timeoutSeconds": 10,
      "maxConsecutiveFailures": 10,
      "portIndex": 0,
      "path": "/",
      "protocol": "MESOS_HTTP",
      "ignoreHttp1xx": false
    }
  ],
  "requirePorts": true
}

Note: You should set acceptedResourceRoles to slave_public. More information about this please check this link.

answered Mar 01 '18 at 05:44

Shui shengbao

18,746
3
27
45

I tried changing hostport to 80. It is unable to deploy application – Sumanth Itha Mar 01 '18 at 07:09
Yes, I meet same error, but I modify you json file. You could copy my json, it will work. – Shui shengbao Mar 01 '18 at 07:10
You need add ` "acceptedResourceRoles": [ "slave_public" ],` – Shui shengbao Mar 01 '18 at 07:11
This is my test result https://imgur.com/a/x7BB9 I suggest you could try. – Shui shengbao Mar 01 '18 at 07:15
I have copied the json provided in the comment that did not even deploy application – Sumanth Itha Mar 01 '18 at 07:21
If possible, could you copy all of the json file. I notice, there are mistakes in your json file, for example `healthChecks` is not effective – Shui shengbao Mar 01 '18 at 07:23
I check it, it seems it is same with my json file? Do you get some error log? – Shui shengbao Mar 01 '18 at 07:41
Another question, do you use Azure Container Service(DC/OS)? – Shui shengbao Mar 01 '18 at 07:42
Yes. I am using Azure Container Service (DC/OS) No it is not getting deployed . I dont have any log https://jsfiddle.net/rxp5zhtk/ – Sumanth Itha Mar 01 '18 at 07:43
It is very strange, the json file works for me fine. You could check this http://shuidcagents.centralus.cloudapp.azure.com/ – Shui shengbao Mar 01 '18 at 07:44
Any rules we need to add for this. I have http and https enabled apart from the rules given by azure. I cant even deploy so i am not sure what i need to add – Sumanth Itha Mar 01 '18 at 07:46
What do you mean `I have http and https enabled apart from the rules given by azure.`? If possible, could you show some screenshot about your marathon UI? – Shui shengbao Mar 01 '18 at 07:50
I have a difference with you. I use a tunnle to connect DC/OS https://imgur.com/a/zvtaF – Shui shengbao Mar 01 '18 at 09:10
But I suggest you could create a container by using UI not json file, like this https://learn.microsoft.com/en-us/azure/container-service/dcos-swarm/container-service-mesos-marathon-ui#deploy-a-docker-formatted-container – Shui shengbao Mar 01 '18 at 09:11
You only need to modify image, I test in my lab, it really works for me. – Shui shengbao Mar 01 '18 at 09:20
I am able to deploy when I tunnel it. But if I use my fqn it is going to dcos ui... https://imgur.com/a/rQOjX – Sumanth Itha Mar 01 '18 at 09:27
According to Azure's official document, Azure suggest us using tunnel it and create a container. – Shui shengbao Mar 01 '18 at 09:29
I think it is not security to expose the UI on the Internet, I test it in my lab, I could not access your UI without authentication. I suggest you should not open port 80 on master VM's NSG. – Shui shengbao Mar 01 '18 at 09:39
I am still unable to see the UI. that you are able to look at – Sumanth Itha Mar 01 '18 at 11:03
I have not allowed 80 in master NSG and UI is not exposed now. It is removed. still i am unable to access using master fqn. Now i am getting This site can’t be reached error – Sumanth Itha Mar 01 '18 at 14:21
@user2547194 You should use agent FQDN to access the service, not master ip. Like this `http://shuidcagents.centralus.cloudapp.azure.com/` – Shui shengbao Mar 02 '18 at 01:04
The master IP is like `shuidcmgmt.***`, the agent IP is like `shuidcagent.***`. You should use agent IP to access your service. – Shui shengbao Mar 02 '18 at 01:44
Do you deploy the image, you should access `http://ggktechagent.southeastasia.cloudapp.azure.com/` – Shui shengbao Mar 02 '18 at 05:05
Can we have application hosted at different ports other than 80? How – Sumanth Itha Mar 02 '18 at 10:14
Yes, it is possible. But you need open port on Azure NSG and LB – Shui shengbao Mar 05 '18 at 02:59
For master or agent ... is it a custom port ? – Sumanth Itha Mar 05 '18 at 06:41
You should open port on agent VM. You don't need open other port on master node. Master is just a management console. The service is running on agent node. – Shui shengbao Mar 05 '18 at 06:42
Let us [continue this discussion in chat](https://chat.stackoverflow.com/rooms/166237/discussion-between-user2547194-and-shengbao-shui-msft). – Sumanth Itha Mar 05 '18 at 11:29

score 1 · Answer 2 · answered Mar 02 '18 at 06:57

1

Along with the above-mentioned JSON I need to use the agent URL to access the application. I was missing on that

answered Mar 02 '18 at 06:57

Sumanth Itha

89
1
9

unable to access helloworld App deployed using DCOS Marathon in Azure

2 Answers2