Docker 网络 - nginx:在上游找不到 [emerg] 主机 [英] Docker Networking - nginx: [emerg] host not found in upstream

查看:44
本文介绍了Docker 网络 - nginx:在上游找不到 [emerg] 主机的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我最近开始迁移到 Docker 1.9 和 Docker-Compose 1.5 的网络功能以替换使用链接.

I have recently started migrating to Docker 1.9 and Docker-Compose 1.5's networking features to replace using links.

到目前为止,使用链接,nginx 连接到我的 php5-fpm fastcgi 服务器没有问题,该服务器位于一个组中的另一台服务器中,通过 docker-compose.最近,当我运行 docker-compose --x-networking up 时,我的 php-fpm、mongo 和 nginx 容器会启动,但是 nginx 立即退出 [emerg] 1#1: host在/etc/nginx/conf.d/default.conf:16

So far with links there were no problems with nginx connecting to my php5-fpm fastcgi server located in a different server in one group via docker-compose. Newly though when I run docker-compose --x-networking up my php-fpm, mongo and nginx containers boot up, however nginx quits straight away with [emerg] 1#1: host not found in upstream "waapi_php_1" in /etc/nginx/conf.d/default.conf:16

但是,如果我在 php 和 mongo 容器正在运行(nginx 退出)时再次运行 docker-compose 命令,nginx 将启动并从那时起正常工作.

However, if I run the docker-compose command again while the php and mongo containers are running (nginx exited), nginx starts and works fine from then on.

这是我的 docker-compose.yml 文件:

nginx:
  image: nginx
  ports:
    - "42080:80"
  volumes:
    - ./config/docker/nginx/default.conf:/etc/nginx/conf.d/default.conf:ro

php:
  build: config/docker/php
  ports:
    - "42022:22"
  volumes:
    - .:/var/www/html
  env_file: config/docker/php/.env.development

mongo:
  image: mongo
  ports:
    - "42017:27017"
  volumes:
    - /var/mongodata/wa-api:/data/db
  command: --smallfiles

这是我用于 nginx 的 default.conf:

This is my default.conf for nginx:

server {
    listen  80;

    root /var/www/test;

    error_log /dev/stdout debug;
    access_log /dev/stdout;

    location / {
        # try to serve file directly, fallback to app.php
        try_files $uri /index.php$is_args$args;
    }

    location ~ ^/.+.php(/|$) {
        # Referencing the php service host (Docker)
        fastcgi_pass waapi_php_1:9000;

        fastcgi_split_path_info ^(.+.php)(/.*)$;
        include fastcgi_params;

        # We must reference the document_root of the external server ourselves here.
        fastcgi_param SCRIPT_FILENAME /var/www/html/public$fastcgi_script_name;

        fastcgi_param HTTPS off;
    }
}

如何让 nginx 只使用一个 docker-compose 调用?

How can I get nginx to work with only a single docker-compose call?

推荐答案

有可能使用volumes_from"作为解决方法,直到引入了depends_on 功能(在下面讨论).您所要做的就是更改您的 docker-compose 文件,如下所示:

There is a possibility to use "volumes_from" as a workaround until depends_on feature (discussed below) is introduced. All you have to do is change your docker-compose file as below:

nginx:
  image: nginx
  ports:
    - "42080:80"
  volumes:
    - ./config/docker/nginx/default.conf:/etc/nginx/conf.d/default.conf:ro
  volumes_from:
    - php

php:
  build: config/docker/php
  ports:
    - "42022:22"
  volumes:
    - .:/var/www/html
  env_file: config/docker/php/.env.development

mongo:
  image: mongo
  ports:
    - "42017:27017"
  volumes:
    - /var/mongodata/wa-api:/data/db
  command: --smallfiles

上述方法中的一个重要警告是,php 的数量会暴露给 nginx,这是不希望的.但目前这是可以使用的一种特定于 docker 的解决方法.

One big caveat in the above approach is that the volumes of php are exposed to nginx, which is not desired. But at the moment this is one docker specific workaround that could be used.

depends_on 功能这可能是一个未来主义的答案.因为该功能尚未在 Docker 中实现(从 1.9 开始)

depends_on feature This probably would be a futuristic answer. Because the functionality is not yet implemented in Docker (as of 1.9)

Docker 引入的新网络特性中,有一个提议引入了depends_on".但是关于相同的@ https://github.com/docker/compose/issues/374 因此,一旦实现,功能depends_on 可用于命令容器启动,但目前,您必须求助于以下方法之一:

There is a proposal to introduce "depends_on" in the new networking feature introduced by Docker. But there is a long running debate about the same @ https://github.com/docker/compose/issues/374 Hence, once it is implemented, the feature depends_on could be used to order the container start-up, but at the moment, you would have to resort to one of the following:

  1. 让 nginx 重试,直到 php 服务器启动 - 我更喜欢这个
  2. 如上所述使用 volums_from 解决方法 - 我会避免使用它,因为体积会泄漏到不必要的容器中.

这篇关于Docker 网络 - nginx:在上游找不到 [emerg] 主机的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆