Running multiple docker-compose files with nginx reverse proxy

后端 未结 1 668
北海茫月
北海茫月 2021-02-09 13:25

I asked a question here and got part of my problem solved, but I was advised to create another question because it started to get a bit lengthy in the comments.

I\'m try

相关标签:
1条回答
  • 2021-02-09 14:28

    I would suggest to extract the nginx-proxy to a separate docker-compose.yml and create a repository for the "reverse proxy" configuration with the following:

    A file with extra contents to add to /etc/hosts

    127.0.0.1 dockertest.com
    127.0.0.1 anothertest.com
    127.0.0.1 third-domain.net
    

    And a docker-compose.yml which will have only the reverse proxy

    version: "3.3"
    services:
      nginx-proxy:
        image: jwilder/nginx-proxy
        ports:
          - 80:80
        volumes:
          - /var/run/docker.sock:/tmp/docker.sock:ro
    

    Next, as you already mentioned, create a docker-compose.yml for each of your repositories that act as web endpoints. You will need to add VIRTUAL_HOST env var to the services that serve your applications (eg. Apache).

    The nginx-proxy container can run in "permanent mode", as it has a small footprint. This way whenever you start a new container with VIRTUAL_HOST env var, the configuration of nginx-proxy will be automatically updated to include the new local domain. (You will still have to update /etc/hosts with the new entry).


    If you decide to use networks, your web endpoint containers will have to be in the same network as nginx-proxy, so your docker-compose files will have to be modified similar to this:

    # nginx-proxy/docker-compose.yml
    version: "3.3"
    services:
      nginx-proxy:
        image: jwilder/nginx-proxy
        ports:
          - 80:80
        networks:
          - reverse-proxy
        volumes:
          - /var/run/docker.sock:/tmp/docker.sock:ro
    networks:
      reverse-proxy:
    
    # service1/docker-compose.yml
    
    version: "3.3"
    services:
      php1:
        ...
        networks:
          - backend1
      apache1:
        ...
        networks:
          - nginx-proxy_reverse-proxy
          - backend1
        environment:
          - VIRTUAL_HOST=dockertest.com
      mysql1:
        ...
        networks:
          - backend1
    networks:
      backend1:
      nginx-proxy_reverse-proxy:
        external: true
    
    # service2/docker-compose.yml
    
    version: "3.3"
    services:
      php2:
        ...
        networks:
          - backend2
      apache2:
        ...
        networks:
          - nginx-proxy_reverse-proxy
          - backend2
        environment:
          - VIRTUAL_HOST=anothertest.com
      mysql2:
        ...
        networks:
          - backend2
    networks:
      backend2:
      nginx-proxy_reverse-proxy:
        external: true
    

    The reverse-proxy network that is created in nginx-proxy/docker-compose.yml is referred as nginx-proxy_reverse-proxy in the other docker-compose files because whenever you define a network - its final name will be {{folder name}}_{{network name}}


    If you want to have a look at a solution that relies on browser proxy extension instead of /etc/hosts, check out mitm-proxy-nginx-companion

    0 讨论(0)
提交回复
热议问题