vaultwarden/hooks
Jeremy Lin 96ff32fb2f
Remove arm32v6-specific tag
This section of code seems to be breaking the Docker release workflow as of a
few days ago, though it's unclear why. This tag only existed to work around
an issue with Docker pulling the wrong image for ARMv6 platforms; that issue
was resolved in Docker 20.10.0, which has been out for a few years now, so it
seems like a reasonable time to drop this tag.
2023-01-24 12:33:25 -08:00
..
arches.sh Support all DB's for Alpine and Debian 2021-12-26 21:59:28 +01:00
build Optimize release workflow. 2021-09-13 14:42:15 +02:00
pre_build Add org.opencontainers labels to Docker images 2021-01-18 01:10:41 -08:00
push Remove arm32v6-specific tag 2023-01-24 12:33:25 -08:00
README.md Project renaming 2021-04-27 23:18:32 +02:00

The hooks in this directory are used to create multi-arch images using Docker Hub automated builds.

Docker Hub hooks provide these predefined environment variables:

  • SOURCE_BRANCH: the name of the branch or the tag that is currently being tested.
  • SOURCE_COMMIT: the SHA1 hash of the commit being tested.
  • COMMIT_MSG: the message from the commit being tested and built.
  • DOCKER_REPO: the name of the Docker repository being built.
  • DOCKERFILE_PATH: the dockerfile currently being built.
  • DOCKER_TAG: the Docker repository tag being built.
  • IMAGE_NAME: the name and tag of the Docker repository being built. (This variable is a combination of DOCKER_REPO:DOCKER_TAG.)

The current multi-arch image build relies on the original vaultwarden Dockerfiles, which use cross-compilation for architectures other than amd64, and don't yet support all arch/distro combinations. However, cross-compilation is much faster than QEMU-based builds (e.g., using docker buildx). This situation may need to be revisited at some point.

References