vaultwarden/hooks/arches.sh

#!/usr/bin/env bash

# The default Debian-based images support these arches for all database backends.
arches=(
    amd64
    armv6
    armv7
    arm64
)
export arches

if [[ "${DOCKER_TAG}" == *alpine ]]; then
    distro_suffix=.alpine
fi
export distro_suffix
Add support for Quay.io and GHCR.io as registries - Added support for Quay.io - Added support for GHCR.io To enable support for these container image registries the following needs to be added. As `Actions secrets and variables` - `Secrets` - `DOCKERHUB_TOKEN` and `DOCKERHUB_USERNAME` - `QUAY_TOKEN` and `QUAY_USERNAME` As `Actions secrets and variables` - `Variables` - `Repository Variables` - `DOCKERHUB_REPO` - `GHCR_REPO` - `QUAY_REPO` The `DOCKERHUB_REPO` currently configured in `Secrets` can be removed if wanted, probably best after this PR has been merged. If one of the vars/secrets are not configured it will skip that specific registry! 2023-03-23 12:30:07 +01:00			`#!/usr/bin/env bash`

Use Docker Buildx for multi-arch builds The bitwarden_rs code is still cross-compiled exactly as before, but Docker Buildx is used to rewrite the resulting Docker images with correct platform metadata (reflecting the target platform instead of the build platform). Buildx also now handles building and pushing the multi-arch manifest lists. 2021-01-09 02:33:36 -08:00			`# The default Debian-based images support these arches for all database backends.`
Multi-arch image support 2020-06-10 02:01:41 -07:00			`arches=(`
			`amd64`
Use Docker Buildx for multi-arch builds The bitwarden_rs code is still cross-compiled exactly as before, but Docker Buildx is used to rewrite the resulting Docker images with correct platform metadata (reflecting the target platform instead of the build platform). Buildx also now handles building and pushing the multi-arch manifest lists. 2021-01-09 02:33:36 -08:00			`armv6`
			`armv7`
			`arm64`
Multi-arch image support 2020-06-10 02:01:41 -07:00			`)`
Add support for Quay.io and GHCR.io as registries - Added support for Quay.io - Added support for GHCR.io To enable support for these container image registries the following needs to be added. As `Actions secrets and variables` - `Secrets` - `DOCKERHUB_TOKEN` and `DOCKERHUB_USERNAME` - `QUAY_TOKEN` and `QUAY_USERNAME` As `Actions secrets and variables` - `Variables` - `Repository Variables` - `DOCKERHUB_REPO` - `GHCR_REPO` - `QUAY_REPO` The `DOCKERHUB_REPO` currently configured in `Secrets` can be removed if wanted, probably best after this PR has been merged. If one of the vars/secrets are not configured it will skip that specific registry! 2023-03-23 12:30:07 +01:00			`export arches`
Multi-arch image support 2020-06-10 02:01:41 -07:00
			`if [[ "${DOCKER_TAG}" == *alpine ]]; then`
Use Docker Buildx for multi-arch builds The bitwarden_rs code is still cross-compiled exactly as before, but Docker Buildx is used to rewrite the resulting Docker images with correct platform metadata (reflecting the target platform instead of the build platform). Buildx also now handles building and pushing the multi-arch manifest lists. 2021-01-09 02:33:36 -08:00			`distro_suffix=.alpine`
Multi-arch image support 2020-06-10 02:01:41 -07:00			`fi`
Add support for Quay.io and GHCR.io as registries - Added support for Quay.io - Added support for GHCR.io To enable support for these container image registries the following needs to be added. As `Actions secrets and variables` - `Secrets` - `DOCKERHUB_TOKEN` and `DOCKERHUB_USERNAME` - `QUAY_TOKEN` and `QUAY_USERNAME` As `Actions secrets and variables` - `Variables` - `Repository Variables` - `DOCKERHUB_REPO` - `GHCR_REPO` - `QUAY_REPO` The `DOCKERHUB_REPO` currently configured in `Secrets` can be removed if wanted, probably best after this PR has been merged. If one of the vars/secrets are not configured it will skip that specific registry! 2023-03-23 12:30:07 +01:00			`export distro_suffix`