From d02c4ba2c94a784b00f35f3395c4c17cec0b8ca0 Mon Sep 17 00:00:00 2001 From: Oliver Bertuch Date: Sun, 18 Dec 2022 22:55:40 +0100 Subject: [PATCH] ci(ct-base): fix pushing to Docker Hub The Docker Login Actions do not enable logging in to docker.io, but a standard registry. By not overriding the registry, Docker Maven Plugin will use the one supplied by Docker context (which the authorization was done for by docker/login-action) --- .github/workflows/container_base_push.yml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/.github/workflows/container_base_push.yml b/.github/workflows/container_base_push.yml index 120f55984dc..8f440151d0c 100644 --- a/.github/workflows/container_base_push.yml +++ b/.github/workflows/container_base_push.yml @@ -21,7 +21,6 @@ on: env: IMAGE_TAG: unstable - REGISTRY: docker.io jobs: build: @@ -83,4 +82,4 @@ jobs: run: echo "IMAGE_TAG=stable" - if: ${{ github.event_name != 'pull_request' }} name: Deploy multi-arch base container image to Docker Hub - run: mvn -f modules/container-base -Pct deploy -Dbase.image.tag=${{ env.IMAGE_TAG }} -Ddocker.registry=${{ env.REGISTRY }} + run: mvn -f modules/container-base -Pct deploy -Dbase.image.tag=${{ env.IMAGE_TAG }}