Page MenuHomeDevCentral

Install Let's encrypt client as a Docker container
ClosedPublic

Authored by dereckson on Mar 15 2018, 20:02.
Tags
None
Referenced Files
F3783036: D1422.id3625.diff
Tue, Nov 26, 01:47
Unknown Object (File)
Sat, Nov 23, 09:43
Unknown Object (File)
Fri, Nov 22, 21:24
Unknown Object (File)
Fri, Nov 22, 16:10
Unknown Object (File)
Wed, Nov 20, 01:36
Unknown Object (File)
Wed, Nov 20, 01:16
Unknown Object (File)
Sat, Nov 16, 06:44
Unknown Object (File)
Wed, Nov 13, 02:57
Subscribers
None

Details

Summary

The Let's encrypt client certbot is installed according two methods:

  • on regular servers, as a distro/OS package
  • on Docker engines, as a container and a wrapper script

This change takes care of the second method.

The certbot/certbot image is used (previously, the letsencrypt
image on quay.org was used), as officially maintained by EFF.

A certbot wrapper command runs the container with the correct
volumes mounted to be able to generate or renew certificates.

Test Plan
  • salt equatower state.apply roles/paas-docker/docker/images
  • salt equatower state.apply roles/paas-docker/wrappers
  • certbot <some commands>

Diff Detail

Repository
rOPS Nasqueron Operations
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

dereckson created this revision.
Equatower
$ certbot
usage:
  certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ...

Certbot can obtain and install HTTPS/TLS/SSL certificates.  By default,
it will attempt to use a webserver both for obtaining and installing the
certificate.
certbot: error: unrecognized arguments:
This revision is now accepted and ready to land.Mar 15 2018, 20:15
This revision was automatically updated to reflect the committed changes.