gha: release: login-action: Don't specify docker.io registry

For some bizarre reason, the login-action will simply fail to
authenticate to docker.io in it's specified as a registry.  The way to
proceed, instead, is to *not* specify any registry as it'd be used by
default.

Fixes: #6943

Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com>
This commit is contained in:
Fabiano Fidêncio 2023-05-23 22:38:12 +02:00
parent df77fefce8
commit d10c9be603
4 changed files with 0 additions and 4 deletions

View File

@ -17,7 +17,6 @@ jobs:
- name: Login to Kata Containers docker.io
uses: docker/login-action@v2
with:
registry: docker.io
username: ${{ secrets.DOCKER_USERNAME }}
password: ${{ secrets.DOCKER_PASSWORD }}

View File

@ -17,7 +17,6 @@ jobs:
- name: Login to Kata Containers docker.io
uses: docker/login-action@v2
with:
registry: docker.io
username: ${{ secrets.DOCKER_USERNAME }}
password: ${{ secrets.DOCKER_PASSWORD }}

View File

@ -17,7 +17,6 @@ jobs:
- name: Login to Kata Containers docker.io
uses: docker/login-action@v2
with:
registry: docker.io
username: ${{ secrets.DOCKER_USERNAME }}
password: ${{ secrets.DOCKER_PASSWORD }}

View File

@ -33,7 +33,6 @@ jobs:
- name: Login to Kata Containers docker.io
uses: docker/login-action@v2
with:
registry: docker.io
username: ${{ secrets.DOCKER_USERNAME }}
password: ${{ secrets.DOCKER_PASSWORD }}