Wonderful! Can't wait to chuck Travis CI just in time for the end of the year 👍

@arkodg I've made some changes to avoid shell scripts and only rely on buildx bake. This allows us to be sandboxed in CI and locally and therefore Docker itself is enough (will also work on Windows where make is not available):

# Validate vendor
$ docker buildx bake vendor-validate

# golangci-lint
$ docker buildx bake lint

# Run golangci-lint and vendor-validate
$ docker buildx bake validate

# Update vendor
$ docker buildx bake vendor-update

Codecov Report

Merging #3315 (185a460) into main (020bcce) will not change coverage.
The diff coverage is n/a.

❗ Current head 185a460 differs from pull request most recent head 7c8cb3b. Consider uploading reports for the commit 7c8cb3b to get more accurate results

@@           Coverage Diff           @@
##             main    #3315   +/-   ##
=======================================
  Coverage   56.35%   56.35%           
=======================================
  Files         101      101           
  Lines        7307     7307           
=======================================
  Hits         4118     4118           
  Misses       2534     2534           
  Partials      655      655           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 020bcce...7c8cb3b. Read the comment docs.

@milosgajdos As discussed, reviving this PR:

• Use buildx bake and goreleaser-xx for native cross-compilation in the Dockerfile.
• Create artifacts with artifact (current platform) or artifact-all target for cross-compilation:
  • darwin/amd64
  • darwin/arm64
  • linux/amd64
  • linux/arm/v5
  • linux/arm/v6
  • linux/arm/v7
  • linux/arm64
  • linux/ppc64le
  • linux/s390x
• Support Docker multi-platform image
• GitHub Actions
  • On git push tag event semver like v2.8.0:
    • Artifacts will be available in the pipeline through actions/upload-artifact
    • Will create the GitHub Release and push artifacts
    • Will create and push Docker tags distribution/distribution:2.8.0 / distribution/distribution:latest
  • On git push (main branch)
    • Artifacts will be available in the pipeline through actions/upload-artifact
    • Will push Docker tag distribution/distribution:edge
  • On git pull_request event
    • Artifacts will be available in the pipeline through actions/upload-artifact

Everything is already in place on https://github.com/crazy-max/docker-distribution as well as the GitHub Actions pipeline if you want to take a look.

Here is how to build with buildx:

# create builder for multi-arch build and cache feature (see below)
docker buildx create --name distribution-builder --use

# build docker image and output to docker with registry:local tag (default)
docker buildx bake image-local

# build multi-platform image
docker buildx bake image-all

# create the artifact matching your current platform in ./bin
docker buildx bake artifact

# create artifacts for many platforms in ./bin
docker buildx bake artifact-all

# build binary in ./bin/registry
docker buildx bake binary

https://github.com/crazy-max/docker-distribution/runs/4584555911?check_suite_focus=true#step:10:23

https://github.com/crazy-max/docker-distribution/releases/tag/v2.8.0

https://hub.docker.com/r/crazymax/distribution/tags?page=1&ordering=last_updated

OCI test results