Docker容器在主机中无法访问

Question

Some of my containers are running a web server (PHP, NodeJS) in production.

If we take the example of the NodeJS container, this is its configuration

docker-compose.yml

version: '2'
services:
  webapp:
    build: .
    volumes_from:
     - data
    links:
     - db:db
     - redis:redis
    ports:
      - '8080:3000'
    restart: always

  ...

With this configuration, I'm able to access to my webapp through http://example.com:8080/ but I cannot access on my host machine with

$ curl localhost:8080
(Time-out)

I have a Nginx server on my host with this configuration:

example.com.conf

upstream webapp {
   server 127.0.0.1:8080;
}

server {
  listen 80;
  listen [::]:80;

  server_name example.com;

  location / {
    proxy_set_header   X-Real-IP $remote_addr;
    proxy_set_header   HOST $http_host;
    proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header   X-NginX-Proxy true;
    proxy_redirect off;

    proxy_pass http://webapp;
  }

}

But acceding to http://example.com/ throw a 504 Gateway Time-out.

If I try to change port configuration in my docker-compose.yml by '127.0.0.1:8080:3000' the problem still here but cannot access to http://example.com (and http://example.com:8080 but it is the result I want).

This is very strange and I don't have the problem running my app on a fresh server. I'm searching for the root of this issue.

Thanks for your support.

EDIT:

$ netstat -tunlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address        State       PID/Program name
tcp        0      0 127.0.0.11:59712        0.0.0.0:*               LISTEN      -               
udp        0      0 127.0.0.11:33293        0.0.0.0:*                           -               

Web server has to be listening on port 3000 but I have

$ docker-compose logs
webapp_1  | Express server listening on port 3000 in production mode

The server is also running...

$ docker port webapp_1
3000/tcp -> 127.0.0.1:8080

Answer 1

Edit: This should work similar to how you have it, did you try changing: proxy_set_header HOST $http_host; to proxy_set_header HOST $host; in your nginx config?

You could put nginx in your Docker Compose file and let Compose use its own network. If you want to add items in another network, you can specify a custom network, see: https://docs.docker.com/compose/networking/

Otherwise, you can look at the output of ifconfig , etc on your host and see which IP and network Compose is using and what the host is listening to.