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
F11675918: D1422.id3625.diff
Tue, Sep 9, 10:51
Unknown Object (File)
Sun, Sep 7, 07:31
Unknown Object (File)
Sun, Sep 7, 00:40
Unknown Object (File)
Fri, Sep 5, 03:42
Unknown Object (File)
Wed, Sep 3, 00:45
Unknown Object (File)
Mon, Sep 1, 14:15
Unknown Object (File)
Fri, Aug 29, 17:39
Unknown Object (File)
Fri, Aug 29, 17:39
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 Passed
Unit
No Test Coverage
Branch
letsencrypt-for-docker (branched from master)
Build Status
Buildable 2229
Build 2477: arc lint + arc unit

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.