使用Docker时遇到一些问题。我的问题是在使用docker-compose和这个库https://github.com/jwilder/nginx-proxy时理解反向代理
所以我有1个Dockerfile，在这里：
FROM alpine:latest
COPY requirements.txt /tmp/requirements.txt
RUN apk add --no-cache \
g++ \
gcc \
freetds \
ca-certificates \
build-base \
libc-dev \
python3 \
python3-dev \
unixodbc-dev \
bash \
nginx \
uwsgi \
uwsgi-python3 \
supervisor && \
python3 -m ensurepip && \
rm -r /usr/lib/python*/ensurepip && \
pip3 install --no-cache-dir --upgrade --force-reinstall pip setuptools && \
pip3 install -r /tmp/requirements.txt && \
rm /etc/nginx/conf.d/default.conf && \
rm -r /root/.cache
# Copy ODBC Driver
COPY odbc.ini /etc/
COPY odbcinst.ini /etc/
# Copy the Nginx global conf
COPY nginx.conf /etc/nginx/
# Copy the Flask Nginx site conf
COPY flask-site-nginx.conf /etc/nginx/conf.d/
# Copy the base uWSGI ini file to enable default dynamic uwsgi process number
COPY uwsgi.ini /etc/uwsgi/
# Custom Supervisord config
COPY supervisord.conf /etc/supervisord.conf
# Add demo app
COPY ./app /app
# EXPOSE 80
WORKDIR /app
CMD ["/usr/bin/supervisord"]
当我跑
docker build -t name/name . #success
docker run -d --name=container_name -p 80 name/name:latest #success
我跑了
curl -i localhost/page #success
------------和我的问题是在分配的端口内使用nginx-proxy ------------------时理解
docker network create --driver bridge reverse-proxy
docker run -d -p 81:80 -p 444:443 \
--name reverse-proxy \
--net=reverse-proxy \
-v /var/run/docker.sock:/tmp/docker.sock:ro \
jwilder/nginx-proxy
这里是我的docker-compose.yml
version: "3"
services:
atk-request:
build: ./_atkrequest #path which Dockerfile is exists
container_name: api-atkrequest
restart: always
networks:
- reverse-proxy
# ports:
# - 80:80 #host:container
expose:
- 80
environment:
- VIRTUAL_HOST=atkrequest.api.dev #nginx-proxy host
- VIRTUAL_PORT=80 #nginx-proxy port
networks:
reverse-proxy:
external:
name: reverse-proxy
然后运行
docker-compose up -d #success without error
并输出docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
ca95a0f42de2 atkrequest_atk-request "/usr/bin/supervisord" 5 seconds ago Up 3 seconds 80/tcp api-atkrequest
c42a9f9d85b5 jwilder/nginx-proxy "/app/docker-entrypoâ¦" About a minute ago Up About a minute 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp reverse-proxy
当调用url时出现curl错误代码503 Service Temporary UnAvailable
curl -i localhost
HTTP/1.1 503 Service Temporarily Unavailable
Server: nginx/1.14.0
Date: Wed, 10 Oct 2018 07:39:09 GMT
Content-Type: text/html
Content-Length: 213
Connection: keep-alive
<html>
<head><title>503 Service Temporarily Unavailable</title></head>
<body bgcolor="white">
<center><h1>503 Service Temporarily Unavailable</h1></center>
<hr><center>nginx/1.14.0</center>
</body>
</html>
然后我被困在这里......
谢谢我
jwilder/nginx-proxy生成一个Nginx default.conf，其中包含已定义VIRTUAL_HOST的每个容器的条目。
由于您已在其中一个容器上定义了VIRTUAL_HOST=atkrequest.api.dev，因此生成的default.conf将具有类似的功能
# atkrequest.api.dev
upstream atkrequest.api.dev {
## Can be connected with "{{dir_name}}_default" network
# {{dir_name}}_atk-request
server {{atk-request container ip}}:80;
}
server {
server_name atkrequest.api.dev;
listen 80 ;
access_log /var/log/nginx/access.log vhost;
location / {
proxy_pass http://atkrequest.api.dev;
}
}
但是没有任何配置为localhost，因为没有你的容器有VIRTUAL_HOST=localhost定义。所以当你请求到达nginx-proxy时 - 它会回应503，因为它没有localhost的任何配置。
如果你想保持nginx-proxy并能够使用atk-request访问localhost容器 - 将它的环境变量更改为VIRTUAL_HOST=localhost。 （Overkill技术，因为你可以简单地暴露端口80:80而不是使用nginx-proxy，但我将其包含在解释中）
如果你想用atk-request访问atkrequest.api.dev容器 - 只需将127.0.0.1 atkrequest.api.dev添加到你的/etc/hosts。