upstream/certbot
1
0
Fork 0
mirror of https://github.com/certbot/certbot.git synced 2026-06-15 11:39:12 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 2
certbot/tools/docker/README.md
humanoid2050 accee97476 bugfixes
2023-03-06 18:39:25 -05:00

2.4 KiB
Raw Permalink Blame History

Running Certbot in Docker

Docker is an amazingly simple and quick way to obtain a certificate. However, this mode of operation is unable to install certificates automatically or configure your webserver, because our installer plugins cannot reach your webserver from inside the Docker container.

Most users should install Certbot by following the installation instructions at https://certbot.eff.org/instructions. You should only use Docker if you are sure you know what you are doing (you understand volumes) and have a good reason to do so, such as following the one service per container rule.

For more information, please read Certbot - Running with Docker.

Certbot Docker Tools

Goal

This code is used to build and deploy new versions of the Certbot and Certbot DNS plugin Docker images to Docker Hub.

High-level behavior

Running ./build.sh all causes the Docker images to be built for all supported architectures. The generated images are stored in a docker cache backed by the local filesystem.

Running ./test.sh all either loads images from the filesystem cache or generates said images on demand, and runs a test command to validate the image contents.

Running ./deploy.sh <TAG> all will push the previously generated images to Docker Hub. The argument is an identifier applied to all docker images and manifests. it may be something like nightly or v2.3.2. If the tag is a version stamp greater than v2.0.0, then a latest tag will also be generated and pushed to the docker hub repo. The per-architecture images are accessible through the corresponding multi-arch manifest by using the docker pull --platform <platform spec> <IMAGE>:<TAG> command.

Configuration

To run these scripts you need:

  1. A computer with Docker installed and the Docker daemon running. You probably don't want to use the docker snap as these scripts have failed when using that in the past.
  2. To be logged into Docker Hub with an account able to push to the Certbot and Certbot DNS Docker images on Docker Hub. Altering the value of DOCKER_HUB_ORG in lib/common will allow you to push to your own account for testing.