问题原文
原帖链接 · Eduardo Oliveira · CC BY-SA 3.0
I have a docker-compose that creates a container with a http server that doesn't get picked up by jwilder's nginx reverse proxy but it works wen instantiated by hand.
version: '2'
services:
mongo:
image: tutum/mongodb
expose:
- "27017"
environment:
- AUTH=no
backend:
build:
context: "./instance"
hostname: instance
ports:
- "1080:8080"
expose:
- "8080"
links:
- mongo
frontend:
build:
context: "./instancegui"
ports:
- "80"
environment:
- VIRTUAL_HOST=some.host.com
- LETSENCRYPT_HOST=some.host.com
- LETSENCRYPT_EMAIL=[email omitted]
the config file generated by the reverse proxy says upstream{...DOWN}
but the container runs fine when instantiated like so
docker run --name group_frontend_1 -p 80 -e "VIRTUAL_HOST=some.host.com" -e "LETSENCRYPT_HOST=some.host.com" -e "LETSENCRYPT_EMAIL=[email omitted]" -d db70e6003db9
已采纳解答
原帖链接 · Eduardo Oliveira · CC BY-SA 3.0
Ok found the solution
the problem is that the contained is not in a network watched by the proxy container, the most direct way is to set the contained in bridge mode
network_mode: "bridge"
and ports 80 is overkill its only needed expose
expose:
- "80"
sources:
https://github.com/jwilder/nginx-proxy/issues/552
https://github.com/docker/compose/issues/3012
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
