Container unreachable externally?

[dbuijs]

I can't seem to access the docker-tikaserver outside the host it is running on. I'm not sure if this is deliberate or not, but it was unexpected.

As per the README:

docker run -d -p 9998:9998 logicalspark/docker-tikaserver

Will start up fine and is reachable locally both through localhost:9998/tika and [public IP]:9998/tika.

[public IP]:9998/tika is not reachable from outside the host. Other docker images with similar starting parameters are.

Is there any documentation available that shows how to make the docker container accessible externally?

[vladholubiev]

I haven't tried to reach my containers from other host, but almost sure this has nothing to do with Tika.

On the other hand, I just noticed there is -h 0.0.0.0 set on the last line of Dockerfile, but this also should be fine.

Could you please provide a code snippet you use to check availability of your containers outside?

[dbuijs]

Within the host that is running Docker (fresh DigitalOcean image, Docker 17.05.0-ce on Ubuntu 16.04), with this startup command:

docker run -d -p 9998:9998 logicalspark/docker-tikaserver

I can reach the tika service with the following commands, as expected:

curl http://localhost:9998/tika
curl http://[Public IP]:9998/tika

From an external host, I can ping the Docker host successfully, and I can access Docker webservices that I launch on the same host next to tikaserver (I used adminer to test). When I attempt to contact the tikaserver from this machine that can ping the Docker host and access other Dockerized webservices on the Docker host:

curl http://[Public IP]:9998/tika

I get this error:

curl: (7) Failed to connect to [Public IP] port 9998: Connection refused

Lastly, I can reach the service from outside with a Putty SSH Tunnel that forwards localhost:9998 to [Public IP]:9998.

[dameikle]

Hello. This container should be accessible externally for you by default. Are you still having this issue? What host OS and docker version are you on?