我正在尝试将jwilder/nginx-proxy设置为反向代理,以代理对公开VIRTUAL_HOST = example.com环境变量的各种容器的请求。
如果容器是直接在ec2群集主机上启动的,则安装将起作用,但会失败,并显示以下错误:“错误运行通知命令:nginx -s reload,退出状态1”(如果它是从ECS产生的。)
运行jwilder / nginx-proxy容器的容器的docker日志:
WARNING: /etc/nginx/dhparam/dhparam.pem was not found. A pre-generated dhparam.pem will be used for now while a new one
is being generated in the background. Once the new dhparam.pem is in place, nginx will be reloaded.
forego | starting dockergen.1 on port 5000
forego | starting nginx.1 on port 5100
dockergen.1 | 2018/08/19 10:43:37 Generated '/etc/nginx/conf.d/default.conf' from 4 containers
dockergen.1 | 2018/08/19 10:43:37 Running 'nginx -s reload'
dockergen.1 | 2018/08/19 10:43:37 **Error running notify command: nginx -s reload, exit status 1**
dockergen.1 | 2018/08/19 10:43:37 Watching docker events
dockergen.1 | 2018/08/19 10:43:37 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload'
2018/08/19 10:48:23 [emerg] 38#38: no servers are inside upstream in /etc/nginx/conf.d/default.conf:55
nginx: [emerg] no servers are inside upstream in /etc/nginx/conf.d/default.conf:55
Generating DH parameters, 2048 bit long safe prime, generator 2
This is going to take a long time
dhparam generation complete, reloading nginx
环境配置如下:
services:
- name: proxy
*volumes*:
Name: docker-socket
Source Path: /var/run/docker.sock
*containers*:
- name: proxy
image: jwilder/nginx-proxy
port: 80:80
Mount Points:
Container Path: /tmp/docker.sock
Source Volume: docker-socket
Read only: true
- name: site
*containers*:
- name: site
image: nginx
port: 0:80
environment:
- VIRTUAL_HOST=example.com
测试命令:
curl -H "Host: example.com" localhost:80
现在它返回默认的nginx页面,因为nginx配置文件由于上游主机丢失而无法生成有效的配置。
生成的无效nginx配置
proxy_set_header Proxy "";
server {
server_name _; # This is just an invalid value which will never trigger on a real hostname.
listen 80;
access_log /var/log/nginx/access.log vhost;
return 503;
}
# example.com
upstream example.com {
}
server {
server_name example.com;
listen 80 ;
access_log /var/log/nginx/access.log vhost;
location / {
proxy_pass http://example.com
}
}
如果使用以下命令,则代理将按预期工作:
docker run -d -p 80:80 -v /var/run/docker.sock:/tmp/docker.sock:ro jwilder/nginx-proxy
如果运行以上命令,它将给出以下输出:
WARNING: /etc/nginx/dhparam/dhparam.pem was not found. A pre-generated dhparam.pem will be used for now while a new one
is being generated in the background. Once the new dhparam.pem is in place, nginx will be reloaded.
forego | starting dockergen.1 on port 5000
forego | starting nginx.1 on port 5100
dockergen.1 | 2018/08/19 10:18:48 Generated '/etc/nginx/conf.d/default.conf' from 10 containers
dockergen.1 | 2018/08/19 10:18:48 Running 'nginx -s reload'
dockergen.1 | 2018/08/19 10:18:48 Watching docker events
dockergen.1 | 2018/08/19 10:18:48 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload'
2018/08/19 10:19:09 [notice] 40#40: signal process started
Generating DH parameters, 2048 bit long safe prime, generator 2
This is going to take a long time
dhparam generation complete, reloading nginx
生成的有效nginx配置:
proxy_set_header Proxy "";
server {
server_name _; # This is just an invalid value which will never trigger on a real hostname.
listen 80;
access_log /var/log/nginx/access.log vhost;
return 503;
}
# example.com
upstream example.com {
## Can be connected with "bridge" network
# ecs-site-site-add8hjasd
server 172.17.0.3:80;
}
server {
server_name example.com;
listen 80 ;
access_log /var/log/nginx/access.log vhost;
location / {
proxy_pass http://example.com;
}
}
我的问题是:为什么这不起作用,是因为权限还是挂载到Docker套接字?
答案 0 :(得分:1)
3天前,我们的团队遇到了这个问题。我们花了很多时间。
问题原因应该在AWS ecs-agent中(我们有2个环境,一个ecs-agent的版本是1.21,另一个是1.24)
昨天,我们解决了这个问题:使用AWS控制台将ecs-agent更新到最新版本:1.34,然后重新启动ecs-agent(docker contianer),就解决了这个问题。
只需在此处粘贴此解决方案。希望对其他人有帮助!
答案 1 :(得分:0)
首先,最好避免在Nginx配置中使用域名,尤其是在定义上游服务器时。如果没有别的,那会令人困惑。
您对example.com
的所有值是否都相同?如果是这样,则您有一个上游块以名称example.com
定义了一个上游服务器集群,那么您有一个服务器块,其服务器名称指令为example.com
,然后您尝试将proxy_pass传递到{{1 }}。
通常,如果您有多个能够处理同一请求的服务器,则将上游块指定为负载平衡方法。编辑上游区块并包含所有上游服务器address:port,如果需要,您可以包括其他选项来配置Nginx如何在它们之间分配负载,有关更多信息,请参阅Nginx文档。您提供给上游区块的名称仅由Nginx使用,可以是任何名称,请不要在此处使用您的域名。像这样:
example.com
然后在服务器块的upstream dockergroup {
指令的端口之前添加一个IP地址,并将listen
指令更改为proxy_pass
我不确定具体细节,但是根据您所链接页面上的文档:
您可以按VIRTUAL_HOST添加设置,请添加 /etc/nginx/vhost.d下的配置文件。与整个代理范围不同 大小写,允许多个配置文件以任何名称结尾 .conf,每个VIRTUAL_HOST文件必须以 VIRTUAL_HOST。
要解决的重要问题是上游块不能为空,并且上游块的名称不应与网络上的任何域或主机名冲突。从我阅读的内容中,您应该可以使用各种配置选项来解决此问题。