Auth does not work with docker-login action.

[andaag]

I use the following to auth to GCR:

    - name: Login to GCR
      uses: docker/login-action@v2
      with:
        registry: gcr.io
        username: oauth2accesstoken
        password: ${{ steps.auth.outputs.access_token }}

This works fine in combination with

    - name: Build container
      uses: docker/build-push-action@v3
      with:
        push: true
        tags: ${{ steps.meta.outputs.tags }}

However, it doesn't work with kaniko, as that requires a username/password.

I'm using federated authentication, so I don't generate any passwords at all in this setup.

[andaag]

Looks like int128/kaniko-action#128 is relevant as well, even though its not the same action.

[bymarshall]

Hi @andaag I made a kaniko github action that may can be useful for your setup bymarshall/kaniko-action . This action support GKE workload identity as authentication method and it's also compatible with docker/login-action.. However, if your are using Workload identity federation I think you could avoid this step since workload identity federation works very similar to workload identity in GKE and no user nor passwords are required.