This repository has been archived on 2020-08-01. You can view files and clone it, but cannot push or open issues or pull requests.
nginx-proxy/Dockerfile

35 lines
1.1 KiB
Text
Raw Normal View History

2015-06-20 22:25:52 +02:00
FROM nginx:1.9.2
2014-05-05 18:59:23 +02:00
MAINTAINER Jason Wilder jwilder@litl.com
# Install wget and install/updates certificates
RUN apt-get update \
&& apt-get install -y -q --no-install-recommends \
ca-certificates \
wget \
&& apt-get clean \
&& rm -r /var/lib/apt/lists/*
# Configure Nginx and apply fix for very long server names
RUN echo "daemon off;" >> /etc/nginx/nginx.conf \
&& sed -i 's/^http {/&\n server_names_hash_bucket_size 128;/g' /etc/nginx/nginx.conf
# Install Forego
RUN wget -P /usr/local/bin https://godist.herokuapp.com/projects/ddollar/forego/releases/current/linux-amd64/forego \
&& chmod u+x /usr/local/bin/forego
2014-05-05 18:59:23 +02:00
ENV DOCKER_GEN_VERSION 0.4.1
2014-06-07 21:53:16 +02:00
RUN wget https://github.com/jwilder/docker-gen/releases/download/$DOCKER_GEN_VERSION/docker-gen-linux-amd64-$DOCKER_GEN_VERSION.tar.gz \
&& tar -C /usr/local/bin -xvzf docker-gen-linux-amd64-$DOCKER_GEN_VERSION.tar.gz \
&& rm /docker-gen-linux-amd64-$DOCKER_GEN_VERSION.tar.gz
COPY . /app/
WORKDIR /app/
2014-05-05 18:59:23 +02:00
ENV DOCKER_HOST unix:///tmp/docker.sock
Add SSL support This adds SSL support for containers. It supports single host certificates, wildcards and SNI using naming conventions for certificates or optionally specify a cert name (for SNI). The SSL cipher configuration is based on mozilla intermediate profile which should provide compatibility with clients back to Firefox 1, Chrome 1, IE 7, Opera 5, Safari 1, Windows XP IE8, Android 2.3, Java 7. The configuration also enables OCSP stapling, HSTS, and ssl session caches. To enable SSL, nginx-proxy should be started w/ -p 443:443 and -v /path/to/certs:/etc/nginx/certs. Certificates must be named: <virtualhost>.crt and <virtualhost>.key where <virtualhost> matches the a value of VIRTUAL_HOST on a container. For wildcard certificates, the certificate and private key should be named after the wildcard domain with .crt and .key suffixes. For example, *.example.com should be name example.com.crt and example.com.key. For SNI where a certificate may be used for multiple domain names, the container can specify a CERT_NAME env var that corresponds to the base file name of the certificate and key. For example, if you have a cert allowing *.example.com and *.bar.com, it can be name shared.crt and shared.key. A container can use that cert by having CERT_NAME=shared and VIRTUAL_HOST=foo.example.com. The name "shared" is arbitrary and can be whatever makes sense. The behavior for the proxy when port 80 and 443 is defined is as follows: * If a container has a usable cert, port 80 will redirect to 443 for that container to always prefer HTTPS when available. * If the container does not have a usable cert 503 will be returned. In the last case, a self-signed or generic cert can be defined as "default.crt" and "default.key" which will allow a client browser to at least make a SSL connection.
2014-11-26 18:38:51 +01:00
VOLUME ["/etc/nginx/certs"]
ENTRYPOINT ["/app/docker-entrypoint.sh"]
CMD ["forego", "start", "-r"]