name: master-latest on: push: branches: [ master ] jobs: multiarch-to-dockerhub-latest: runs-on: ubuntu-latest steps: - name: Checkout uses: actions/checkout@v2 # Setup qEMU for arm64 - name: Set up QEMU uses: docker/setup-qemu-action@v1 with: platforms: arm64 # We use buildx instead of regular build so we can take advantage of Docker layer cache via GithubActions's cache # Also buildx offers multi-arch builds - name: Set up Docker Buildx id: buildx uses: docker/setup-buildx-action@v1 # Setup the Github Actions cache. - name: Cache Docker layers uses: actions/cache@v2 with: path: /tmp/.buildx-cache key: ${{ runner.os }}-buildxarch-${{ github.sha }} restore-keys: | ${{ runner.os }}-buildxarch- - name: Login to DockerHub uses: docker/login-action@v1 with: username: ${{ secrets.DOCKER_HUB_USERNAME }} password: ${{ secrets.DOCKER_HUB_ACCESS_TOKEN }} # the arm64 is of course much slower due to qemu, so build and push amd64 **first** # due to the way manifests work, the gap between this and the complete push below # could result in pull failures or inconsistencies for arm64, such is life. # further duplicated by building both release and debug builds - name: Build and push amd64 Release Docker Image to DockerHub uses: docker/build-push-action@v2 with: build-args: DEBUG_BUILD=0,BASE_IMAGE_SUFFIX= builder: ${{ steps.buildx.outputs.name }} context: . file: ./Dockerfile platforms: linux/amd64 tags: rpardini/docker-registry-proxy:latest push: true cache-from: type=local,src=/tmp/.buildx-cache/release # first run does not export the cache - name: Build and push amd64 Debug Docker Image to DockerHub uses: docker/build-push-action@v2 with: build-args: DEBUG_BUILD=1,BASE_IMAGE_SUFFIX=-debug builder: ${{ steps.buildx.outputs.name }} context: . file: ./Dockerfile platforms: linux/amd64 tags: rpardini/docker-registry-proxy:latest-debug push: true cache-from: type=local,src=/tmp/.buildx-cache/debug # first run does not export the cache # Do it all again with both archs. the amd64 will be a huge cache hit # this will update the manifest have both arches - name: Build and push multiarch Release Docker Image to DockerHub uses: docker/build-push-action@v2 with: build-args: DEBUG_BUILD=0,BASE_IMAGE_SUFFIX= builder: ${{ steps.buildx.outputs.name }} context: . file: ./Dockerfile platforms: linux/arm64,linux/amd64 tags: rpardini/docker-registry-proxy:latest push: true cache-from: type=local,src=/tmp/.buildx-cache/release cache-to: type=local,mode=max,dest=/tmp/.buildx-cache/release - name: Build and push multiarch Debug Docker Image to DockerHub uses: docker/build-push-action@v2 with: build-args: DEBUG_BUILD=1,BASE_IMAGE_SUFFIX=-debug builder: ${{ steps.buildx.outputs.name }} context: . file: ./Dockerfile platforms: linux/arm64,linux/amd64 tags: rpardini/docker-registry-proxy:latest-debug push: true cache-from: type=local,src=/tmp/.buildx-cache/debug cache-to: type=local,mode=max,dest=/tmp/.buildx-cache/debug