-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Closed
Description
I've updated my proxy image today, and tried to restart all my other containers behind the proxy, however all of them failed, am I doing something wrong? ( i did follow explanations in issue #64, however that didn't help)
proxy
docker run -d --name nginx-proxy \
-p 80:80 -p 443:443 \
--restart=always \
-v /opt/my-certs:/etc/nginx/certs \
-v /var/run/docker.sock:/tmp/docker.sock:ro \
jwilder/nginx-proxy
my dev container (nodejs) built locally and it exposes port 8181
docker run -d --name www.dev1 \
--restart=always \
--link db --link redis \
-e VIRTUAL_PORT=8181 \
-e VIRTUAL_PROTO=https \
-e VIRTUAL_HOST=dev1.mysite.com \
-v /opt/my-volume/web/dev1/:/opt/my-volume/web/ \
-v /opt/my-certs:/opt/my-certs:ro \
-w /opt/my-volume/web/ localhost:5000/www \
bash -c 'npm start server.js'
Right before I run dev container, i can see output of nginx -t
root@fba41f832f35:/app# nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
After I start dev container, i see the following
root@fba41f832f35:/app# nginx -t
2016/05/02 07:15:49 [emerg] 69#69: no servers are inside upstream in /etc/nginx/conf.d/default.conf:34
nginx: [emerg] no servers are inside upstream in /etc/nginx/conf.d/default.conf:34
nginx: configuration file /etc/nginx/nginx.conf test failed
when I check /etc/nginx/conf.d/default.conf i see empty upstream
upstream dev1.mysite.com {
}
Is there anything I am doing wrong? I've been using same startup script for a good 6 month and it used to work right before I pulled the new image, did anything changed? Please help
Metadata
Metadata
Assignees
Labels
No labels