# https://github.com/letsencrypt/lets-encrypt-preview/pull/431#issuecomment-103659297 # it is more likely developers will already have ubuntu:trusty rather # than e.g. debian:jessie and image size differences are negligible FROM ubuntu:trusty MAINTAINER Jakub Warmuz MAINTAINER William Budington # Note: this only exposes the port to other docker containers. You # still have to bind to 443@host at runtime, as per the ACME spec. EXPOSE 443 # TODO: make sure --config-dir and --work-dir cannot be changed # through the CLI (letsencrypt-docker wrapper that uses standalone # authenticator and text mode only?) VOLUME /etc/letsencrypt /var/lib/letsencrypt WORKDIR /opt/letsencrypt # no need to mkdir anything: # https://docs.docker.com/reference/builder/#copy # If doesn't exist, it is created along with all missing # directories in its path. COPY bootstrap/ubuntu.sh /opt/letsencrypt/src/ RUN /opt/letsencrypt/src/ubuntu.sh && \ apt-get clean && \ rm -rf /var/lib/apt/lists/* \ /tmp/* \ /var/tmp/* # the above is not likely to change, so by putting it further up the # Dockerfile we make sure we cache as much as possible COPY setup.py README.rst CHANGES.rst MANIFEST.in /opt/letsencrypt/src/ # all above files are necessary for setup.py, however, package source # code directory has to be copied separately to a subdirectory... # https://docs.docker.com/reference/builder/#copy: "If is a # directory, the entire contents of the directory are copied, # including filesystem metadata. Note: The directory itself is not # copied, just its contents." Order again matters, three files are far # more likely to be cached than the whole project directory COPY letsencrypt /opt/letsencrypt/src/letsencrypt/ COPY acme /opt/letsencrypt/src/acme/ COPY letsencrypt_apache /opt/letsencrypt/src/letsencrypt_apache/ COPY letsencrypt_nginx /opt/letsencrypt/src/letsencrypt_nginx/ RUN virtualenv --no-site-packages -p python2 /opt/letsencrypt/venv && \ /opt/letsencrypt/venv/bin/pip install -e /opt/letsencrypt/src # install in editable mode (-e) to save space: it's not possible to # "rm -rf /opt/letsencrypt/src" (it's stays in the underlaying image); # this might also help in debugging: you can "docker run --entrypoint # bash" and investigate, apply patches, etc. ENV PATH /opt/letsencrypt/venv/bin:$PATH # TODO: is --text really necessary? ENTRYPOINT [ "letsencrypt", "--text" ]