harrise/acme-tiny-server repository overview

⁠Usage

If you already have a key file for you domain, you can share that file with the container. (Assuming your key is located in ./keys)

docker run \
  -v $(pwd)/artifacts:/tmp/ssl/ \
  -v $(pwd)/keys:/var/keys/ \
  -e ACME_HOSTNAME=example.com \
  -e DOMAIN_KEY=/var/keys/domain.key \
  -p 80:80 \
  --rm
  harrise/acme-tiny-server

If not, you can automatically generate one along with your signed certificate.

docker run \
  -v $(pwd)/artifacts:/tmp/ssl \
  -e ACME_HOSTNAME=example.com \
  -p 80:80 \
  --rm \
  harrise/acme-tiny-server

In both cases, your certificates and key files should be stored in /tmp/ssl on the container after running. So you'll need to share that volume with a local directory.

You need to expose port 80 since this is just a nginx web server that hosts some challenge files⁠.

That also means that this has to be run on your actual webserver so that Let's Encrypt can verify domain ownership.

⁠About

Uses acme-tiny⁠ to get a signed certificate from the Let's Encrypt CA. The certificate will be valid for about 3 months.

Check out the acme-tiny README⁠ for more info.