setup-buildx-action: action suddenly failing with no change in workflows

Contributing guidelines

I’ve found a bug, and:

  • The documentation does not mention anything about my problem
  • There are no open or closed issues that are related to my problem

Description

the action repeatedly fails. here’s the error: image

or as text:

Booting builder
  /usr/bin/docker buildx inspect --bootstrap --builder builder-85d1d6d9-4699-4473-8322-ba8e5611d0ea
  #1 [internal] booting buildkit
  #1 pulling image moby/buildkit:buildx-stable-1
  #1 pulling image moby/buildkit:buildx-stable-1 0.2s done
  #1 ERROR: Error response from daemon: Head "https://registry-1.docker.io/v2/moby/buildkit/manifests/buildx-stable-1": unauthorized: incorrect username or password
  ------
   > [internal] booting buildkit:
  ------
  ERROR: Error response from daemon: Head "https://registry-1.docker.io/v2/moby/buildkit/manifests/buildx-stable-1": unauthorized: incorrect username or password
Error: The process '/usr/bin/docker' failed with exit code 1

Expected behaviour

it should set up buildx

Actual behaviour

the action fails

Repository URL

No response

Workflow run URL

No response

YAML workflow

- name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v2


### Workflow logs

Run docker/setup-buildx-action@v2 with: driver: docker-container buildkitd-flags: --allow-insecure-entitlement security.insecure --allow-insecure-entitlement network.host install: false use: true cleanup: true Docker info /usr/bin/docker version Client: Docker Engine - Community Version: 26.1.3 API version: 1.45 Go version: go1.21.10 Git commit: b72abbb Built: Thu May 16 08:33:29 2024 OS/Arch: linux/amd64 Context: default

Server: Docker Engine - Community Engine: Version: 26.1.3 API version: 1.45 (minimum version 1.24) Go version: go1.21.10 Git commit: 8e96db1 Built: Thu May 16 08:33:29 2024 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.7.22 GitCommit: 7f7fdf5fed64eb6a7caf99b3e12efcf9d60e311c runc: Version: 1.1.14 GitCommit: v1.1.14-0-g2c9f560 docker-init: Version: 0.19.0 GitCommit: de40ad0 /usr/bin/docker info Client: Docker Engine - Community Version: 26.1.3 Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.17.1 Path: /usr/libexec/docker/cli-plugins/docker-buildx compose: Docker Compose (Docker Inc.) Version: v2.27.1 Path: /usr/libexec/docker/cli-plugins/docker-compose

Server: Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 15 Server Version: 26.1.3 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Using metacopy: false Native Overlay Diff: false userxattr: false Logging Driver: json-file Cgroup Driver: cgroupfs Cgroup Version: 2 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog Swarm: inactive Runtimes: io.containerd.runc.v2 runc Default Runtime: runc Init Binary: docker-init containerd version: 7f7fdf5fed64eb6a7caf99b3e12efcf9d60e311c runc version: v1.1.14-0-g2c9f560 init version: de40ad0 Security Options: apparmor seccomp Profile: builtin cgroupns Kernel Version: 6.8.0-1014-azure Operating System: Ubuntu 22.04.5 LTS OSType: linux Architecture: x86_64 CPUs: 2 Total Memory: 7.753GiB Name: fv-az1715-685 ID: 50f520d9-697c-4217-af0f-2af166f71cd2 Docker Root Dir: /var/lib/docker Debug Mode: false Username: githubactions Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false

Buildx version /usr/bin/docker buildx version github.com/docker/buildx v0.17.1 257815a6fbaee88976808020bf04274388275ae8 Creating a new builder instance /usr/bin/docker buildx create --name builder-85d1d6d9-4699-4473-8322-ba8e5611d0ea --driver docker-container --buildkitd-flags --allow-insecure-entitlement security.insecure --allow-insecure-entitlement network.host --use builder-85d1d6d9-4699-4473-8322-ba8e5611d0ea Booting builder /usr/bin/docker buildx inspect --bootstrap --builder builder-85d1d6d9-4699-4473-8322-ba8e5611d0ea #1 [internal] booting buildkit #1 pulling image moby/buildkit:buildx-stable-1 #1 pulling image moby/buildkit:buildx-stable-1 0.2s done #1 ERROR: Error response from daemon: Head “https://registry-1.docker.io/v2/moby/buildkit/manifests/buildx-stable-1”: unauthorized: incorrect username or password

[internal] booting buildkit:


ERROR: Error response from daemon: Head “https://registry-1.docker.io/v2/moby/buildkit/manifests/buildx-stable-1”: unauthorized: incorrect username or password Error: The process ‘/usr/bin/docker’ failed with exit code 1


### BuildKit logs

_No response_

### Additional info

_No response_

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 44
  • Comments: 35 (1 by maintainers)

Commits related to this issue

Most upvoted comments

Everyone having a nice Friday? 😃

There’s an active incident: https://www.dockerstatus.com/

From : https://www.dockerstatus.com/

Anonymous pulls and password auth continue to work.

image

Our CI/CD pipelines You Have Failed

This works as a workaround, doing docker logout first:

      - name: Fix Docker Hub Issue
        run: docker logout
        
      - name: Set up Docker Buildx
        id: buildx
        uses: docker/setup-buildx-action@v3.6.1

      - name: Login to GitHub Container Registry
        uses: docker/login-action@v3.3.0
        with:
          registry: ${{ env.DOCKER_REGISTRY }}
          username: ${{ github.repository_owner }}
          password: ${{ secrets.GITHUB_TOKEN }}

And that folks, it’s the reason why you never deploy on friday

Friday vibes

image

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.

Here are all the people who deploy on a Friday? Do it on Monday 😂

we build docker images as part of our CI flow. just because we build an image doesn’t mean we intend to deploy it, but we require the build to succeed to merge to main.

same here!

A workaround is to manually run doker logout before the action itself

      - name: TMP Workaround For Issue
        run: |
          docker logout

      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v3

We are on a forest fire 🔥

same here!