1
0
Fork 1
Spiegel von https://github.com/dani-garcia/vaultwarden.git synchronisiert 2024-11-16 04:12:53 +01:00
vaultwarden/hooks
BlackDex ca0fd7a31b Optimize release workflow.
- Split Debian and Alpine into different build matrix
  This starts building both Debian and Alpine based images at the same time
- Make use of Docker BuildKit, which improves speed also.
- Use BuildKit caching for Rust Cargo across docker images.
  This prevents downloading the same crates multiple times.
- Use Github Actions Services to start a docker registry, starting it
via the build script sometimes caused issues.
- Updated the Build workflow to use Ubuntu 20.04 which is more close to
the Bullseye Debian release regarding package versions.
2021-09-13 14:42:15 +02:00
..
arches.sh Use Docker Buildx for multi-arch builds 2021-01-09 02:33:36 -08: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 Optimize release workflow. 2021-09-13 14:42:15 +02: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