Docker: can not access container host/port

Question

I have a container

ps -a
de3ff650fbef        tasklist-img         "/bin/sh -c 'java -ja"   2 minutes ago       Up 2 minutes               8080/tcp, 0.0.0.0:8080->8081/tcp   tasklist-img-01

And could not access like localhost:8080/task-list

When I inspect I got json with ip address 172.17.0.2, it is also unreachable

},
        "NetworkSettings": {
            "Bridge": "",
            "SandboxID": "82398f58a56f6685223df13f0e053c1ad388505ff595ec270eb4e9a445109641",
            "HairpinMode": false,
            "LinkLocalIPv6Address": "",
            "LinkLocalIPv6PrefixLen": 0,
            "Ports": {
                "8080/tcp": null,
                "8081/tcp": [
                    {
                        "HostIp": "0.0.0.0",
                        "HostPort": "8080"
                    }
                ]
            },
            "SandboxKey": "/var/run/docker/netns/82398f58a56f",
            "SecondaryIPAddresses": null,
            "SecondaryIPv6Addresses": null,
            "EndpointID": "e8d9d3e209e858d6e881295899949df457fd8ca28cb059105bebceb6015e1e7d",
            "Gateway": "172.17.0.1",
            "GlobalIPv6Address": "",
            "GlobalIPv6PrefixLen": 0,
            "IPAddress": "172.17.0.2",
            "IPPrefixLen": 16,
            "IPv6Gateway": "",
            "MacAddress": "02:42:ac:11:00:02",
            "Networks": {
                "bridge": {
                    "IPAMConfig": null,
                    "Links": null,
                    "Aliases": null,
                    "NetworkID": "24ef0b8e2aea470b5a0c4e48b96e5b203ea35b291689fe6d73b71b870c86f659",
                    "EndpointID": "e8d9d3e209e858d6e881295899949df457fd8ca28cb059105bebceb6015e1e7d",
                    "Gateway": "172.17.0.1",
                    "IPAddress": "172.17.0.2",
                    "IPPrefixLen": 16,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "MacAddress": "02:42:ac:11:00:02"
                }
            }

My docker machine run under ip 192.168.99.100 i run container with command

docker run -d -p  8080:8081 --name tasklist-img-01 tasklist-img

I can access http://192.168.99.100:8080/ and it is return only dropwizard metrics, http://192.168.99.100:8080/task-list/ unreachable

I have also log

INFO  [2016-11-14 19:32:29,324] io.dropwizard.server.DefaultServerFactory: Registering admin handler with root path prefix: /
INFO  [2016-11-14 19:32:29,402] org.eclipse.jetty.setuid.SetUIDListener: Opened application@522a32b1{HTTP/1.1}{0.0.0.0:8080}
INFO  [2016-11-14 19:32:29,402] org.eclipse.jetty.setuid.SetUIDListener: Opened admin@35390ee3{HTTP/1.1}{0.0.0.0:8081}
INFO  [2016-11-14 19:32:29,406] org.eclipse.jetty.server.Server: jetty-9.2.z-SNAPSHOT
INFO  [2016-11-14 19:32:30,428] io.dropwizard.jersey.DropwizardResourceConfig: The following paths were found for the configured resources:

    GET     /task-list (com.bjedrzejewski.tasklistservice.TaskListResource)
    GET     /task-list/big (com.bjedrzejewski.tasklistservice.TaskListResource)

INFO  [2016-11-14 19:32:30,435] org.eclipse.jetty.server.handler.ContextHandler: Started i.d.j.MutableServletContextHandler@378bd86d{/,null,AVAILABLE}
INFO  [2016-11-14 19:32:30,450] io.dropwizard.setup.AdminEnvironment: tasks =

    POST    /tasks/log-level (io.dropwizard.servlets.tasks.LogConfigurationTask)
    POST    /tasks/gc (io.dropwizard.servlets.tasks.GarbageCollectionTask)

WARN  [2016-11-14 19:32:30,451] io.dropwizard.setup.AdminEnvironment:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!    THIS APPLICATION HAS NO HEALTHCHECKS. THIS MEANS YOU WILL NEVER KNOW      !
!     IF IT DIES IN PRODUCTION, WHICH MEANS YOU WILL NEVER KNOW IF YOU'RE      !
!    LETTING YOUR USERS DOWN. YOU SHOULD ADD A HEALTHCHECK FOR EACH OF YOUR    !
!         APPLICATION'S DEPENDENCIES WHICH FULLY (BUT LIGHTLY) TESTS IT.       !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
INFO  [2016-11-14 19:32:30,456] org.eclipse.jetty.server.handler.ContextHandler: Started i.d.j.MutableServletContextHandler@7b60c3e{/,null,AVAILABLE}
INFO  [2016-11-14 19:32:30,486] org.eclipse.jetty.server.ServerConnector: Started application@522a32b1{HTTP/1.1}{0.0.0.0:8080}
INFO  [2016-11-14 19:32:30,487] org.eclipse.jetty.server.ServerConnector: Started admin@35390ee3{HTTP/1.1}{0.0.0.0:8081}

So I cant understand where is my micro service?:)))

Why the boot2docker tag? Are you not using the respective native Docker for the OS? — OneCricketeer
– OneCricketeer, Commented Nov 14, 2016 at 19:44
no, I installed DockerToolbox-1.12.2.exe , is it not better?:( — Armen Arzumanyan
– Armen Arzumanyan, Commented Nov 14, 2016 at 19:46
This is not a programming question, and therefore off-topic on SO. Try posting on ServerFault. — BadZen
– BadZen, Commented Nov 14, 2016 at 19:51
@BadZen Feel free to read this post. meta.stackoverflow.com/questions/276579/… — OneCricketeer
– OneCricketeer, Commented Nov 14, 2016 at 19:53

OneCricketeer · Accepted Answer · 2016-11-14 19:57:49Z

2

Looks like you mapped port 8081 of the container to 8080 of the host

docker run -d -p  8080:8081

And there are ports listening on 8080 and 8081

INFO  [2016-11-14 19:32:30,486] org.eclipse.jetty.server.ServerConnector: Started application@522a32b1{HTTP/1.1}{0.0.0.0:8080}
INFO  [2016-11-14 19:32:30,487] org.eclipse.jetty.server.ServerConnector: Started admin@35390ee3{HTTP/1.1}{0.0.0.0:8081}

You can access it, sure, but this is not the true 8080 of the container. You probably need to publish the range of ports

docker run -d -p  8080-8081:8080-8081

edited Nov 14, 2016 at 19:57

answered Nov 14, 2016 at 19:51

OneCricketeer

193k20 gold badges146 silver badges276 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Docker: can not access container host/port

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related