docker / setup-qemu-action

GitHub Action to install QEMU static binaries
https://github.com/marketplace/actions/docker-setup-qemu
Apache License 2.0
459 stars 62 forks source link

Incorrect username and password #168

Closed D3vil0p3r closed 2 months ago

D3vil0p3r commented 2 months ago

Contributing guidelines

I've found a bug, and:

Description

When I run this GitHub Actions job, I get:

Error response from daemon: Head "https://registry-1.docker.io/v2/tonistiigi/binfmt/manifests/latest": unauthorized: incorrect username or password

There is a closed issue https://github.com/docker/setup-qemu-action/issues/167 with comments mentioning my error but I'm still getting this weird behavior.

Expected behaviour

Running with no issue.

Actual behaviour

Error response from daemon: Head "https://registry-1.docker.io/v2/tonistiigi/binfmt/manifests/latest": unauthorized: incorrect username or password

Repository URL

No response

Workflow run URL

No response

YAML workflow

name: Scheduled Container Publish

on:
  schedule:
    - cron: '22 4 * * 0'
  workflow_dispatch:

jobs:
  docker-publish:
    runs-on: ubuntu-latest
    steps:
      -
        name: Set up QEMU
        uses: docker/setup-qemu-action@v3
      -
        name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v3
      - 
        name: Log into registry
        uses: docker/login-action@v3
        with:
          username: ${{ secrets.DOCKER_HUB_USER }}
          password: ${{ secrets.DOCKER_HUB_TOKEN }}
      -
        name: Build and push
        uses: docker/build-push-action@v6
        with:
          push: true
          tags: athenaos/hephaestus:latest

Workflow logs

No response

BuildKit logs

No response

Additional info

No response

pablo-statsig commented 2 months ago

We are also seeing this

T-Klug commented 2 months ago

Also seeing it

alabdao commented 2 months ago

same

morlando016 commented 2 months ago

Also seeing this behavior. I removed what I thought to be unused github secrets so I thought maybe I broke this accidently somehow, but I dont see anywhere where my secrets would have been plugged into this action.

D3vil0p3r commented 2 months ago

@crazy-max can you give a look please?

T-Klug commented 2 months ago

https://www.dockerstatus.com/

Might be a docker issue (although they say anonymous works)

hugoheml commented 2 months ago

Same for me

duboisej commented 2 months ago

Same here

iborysiuk commented 2 months ago

Same for me

hugoheml commented 2 months ago

Resolved for me.

tonistiigi commented 2 months ago

This was hub-side issue with personal access tokens. Should be resolved now.

https://www.dockerstatus.com/

September 27, 2024 14:20 PDT September 27, 2024 21:20 UTC[Monitoring] Access Tokens are working again, and error rates have returned to normal. Will continue to monitor.