upstream/certbot
1
0
Fork 0
mirror of https://github.com/certbot/certbot.git synced 2026-05-28 04:34:11 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

bugfixes

Browse source
This commit is contained in:
humanoid2050 2023-03-06 18:39:25 -05:00
parent d78cde1894
commit accee97476
4 changed files with 29 additions and 25 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
tools/docker/README.md
View file

@ -20,21 +20,21 @@ DNS plugin Docker images to Docker Hub.
High-level behavior
-------------------
Running `./build.sh <TAG> all` causes the Docker images to be built for all
supported architectures, where `<TAG>` is the base of the tag that should be
given to the generated images. The tag should either be `nightly` or a git
version tag like `v2.2.0`. For version tags above `v2.0.0`, additional tags
for `latest` are also generated. The generated images are stored in a local
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 <TAG> all` either loads images from the filesystem cache
or generates said images on demand, loads them into the local docker cache,
and runs a test command to validate the image contents.
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 per-architecture images are accessible through the
corresponding multi-arch manifest by using the `docker pull --platform
<platform spec> <IMAGE>:<TAG>` command.
to Docker Hub. The <TAG> 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
-------------

2
tools/docker/build.sh
View file

@ -14,7 +14,7 @@ set -euxo pipefail
source "$(realpath $(dirname ${BASH_SOURCE[0]}))/lib/common"
REQUESTED_ARCH_LIST=$(InterpretArchRequest "$2")
REQUESTED_ARCH_LIST=$(InterpretArchRequest "$1")
PLATFORM_SPEC=$(archList2platformList "${REQUESTED_ARCH_LIST[@]}")
#jump to root, matching popd handed by Cleanup on EXIT via trap

16
tools/docker/deploy.sh Normal file → Executable file
View file

@ -4,12 +4,16 @@ set -euxo pipefail
# This script builds certbot docker and certbot dns plugins docker using the
# local Certbot files.
# Usage: ./deploy.sh [TAG] [all|<comma separated list of arch identifiers>]
# with the [TAG] value corresponding the base of the tag to give the Docker
# images and the 2nd value being the architecture to build snaps for.
# Values for the tag should be something like `v0.34.0` or `nightly`. The
# given value is only the base of the tag because the things like the CPU
# architecture are also added to the full tag.
# Usage:
# ./deploy.sh <TAG> all
# ./deploy.sh <TAG> <architectures>
# The <TAG> 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 argument "all" will build all know architectures. Alternatively, the
# user may provide a comma separated list of architectures drawn from the
# known architectures. Know architectures include amd64, arm32v6, and arm64v8.
source "$(realpath $(dirname ${BASH_SOURCE[0]}))/lib/common"

14
tools/docker/test.sh
View file

@ -3,16 +3,16 @@ set -euxo pipefail
# This script tests certbot docker and certbot dns plugin images.
# Usage: ./test.sh [TAG] [all|<comma separated list of arch identifiers>]
# with the [TAG] value corresponding the base of the tag to give the Docker
# images and the 2nd value being the architecture to build snaps for.
# Values for the tag should be something like `v0.34.0` or `nightly`. The
# given value is only the base of the tag because the things like the CPU
# architecture are also added to the full tag.
# Usage:
# ./test.sh all
# ./test.sh <architectures>
# The argument "all" will build all know architectures. Alternatively, the
# user may provide a comma separated list of architectures drawn from the
# known architectures. Know architectures include amd64, arm32v6, and arm64v8.
source "$(realpath $(dirname ${BASH_SOURCE[0]}))/lib/common"
REQUESTED_ARCH_LIST=$(InterpretArchRequest "$2")
REQUESTED_ARCH_LIST=$(InterpretArchRequest "$1")
#jump to root, matching popd handed by Cleanup on EXIT via trap
pushd "${REPO_ROOT}"