fatal: could not read Username for 'https://github.com': No such device or address

[stigok]

Behaviour

It seems breaking changes was introduced to tag v2 this weekend. Locking action to 1b7db3498a1941bc89504b474567da7ddc1341c solves the issue.

Steps to reproduce this issue

1. Use docker/build-push-action@v2 with attached workflow file
2. Trigger action

Expected behaviour

It should work as before the weekend using the same tag (@v2)

Actual behaviour

Build fails

Configuration

• Repository URL (if public): private
• Build URL (if public): private

name: "Docker Build/Push and Deploy to k8s"

on:
  push:
    branches:
      - master
  pull_request:
    branches:
      - master

env:
  REGISTRY: private.registry.tld
  IMAGE_NAME: myrepo

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v1
        id: buildx
        with:
          install: true

      - name: Cache Docker layers
        uses: actions/cache@v2
        with:
          path: /tmp/.buildx-cache
          key: ${{ runner.os }}-buildx-${{ github.sha }}
          restore-keys: |
            ${{ runner.os }}-buildx-

      - uses: actions/checkout@v2

      - uses: docker/login-action@v1
        with:
          registry: ${{ env.REGISTRY }}
          username: ${{ secrets.registry_username }}
          password: ${{ secrets.registry_password }}

      - name: Build and push
        uses: docker/build-push-action@v2
        with:
          # Only push if we are on the master branch
          push: ${{ endswith(github.ref, 'master') }}
          tags: "${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:${{ github.sha }}"
          cache-from: type=local,src=/tmp/.buildx-cache
          cache-to: type=local,dest=/tmp/.buildx-cache

Logs

Buildx version: 0.4.2
🏃 Starting build...
/usr/bin/docker buildx build --tag plattform.azurecr.io/myrepo/master:3b9518b1d1444f6307f491a4d8e59692c3df21ea --iidfile /tmp/docker-build-push-AmL3yR/iidfile --cache-from type=local,src=/tmp/.buildx-cache --cache-to type=local,dest=/tmp/.buildx-cache --secret id=GIT_AUTH_TOKEN,src=/tmp/docker-build-push-AmL3yR/tmp-3255-cPRnHGzuxj5J --file ./Dockerfile https://github.com/myorg/myrepo.git#pull/5/merge
time="2020-10-05T08:16:01Z" level=warning msg="invalid non-bool value for BUILDX_NO_DEFAULT_LOAD: "
time="2020-10-05T08:16:01Z" level=warning msg="No output specified for docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load" 
#1 [internal] load git source https://github.com/myorg/myrepo.git#pull/...
#1 0.085 Initialized empty Git repository in /var/lib/buildkit/runc-overlayfs/snapshots/snapshots/1/fs/
#1 0.641 fatal: could not read Username for 'https://github.com': No such device or address
#1 ERROR: failed to fetch remote https://github.com/myorg/myrepo.git: exit status 128 
------
 > [internal] load git source https://github.com/myorg/myrepo.git#pull/5/merge:
------
failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to read dockerfile: failed to load cache key: failed to fetch remote https://github.com/myorg/myrepo.git: exit status 128 
Error: The process '/usr/bin/docker' failed with exit code 1

[crazy-max]

@stigok Looks like an issue with Git context. Can you use Path context in the meantime? (add context: . input):

     - name: Build and push
        uses: docker/build-push-action@v2
        with:
          # Only push if we are on the master branch
          context: .
          push: ${{ endswith(github.ref, 'master') }}
          tags: "${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:${{ github.sha }}"
          cache-from: type=local,src=/tmp/.buildx-cache
          cache-to: type=local,dest=/tmp/.buildx-cache

[BobCashStory]

@crazy-max look to work with context in my side, maybe add it on the readme 👍

[stigok]

Pipeline works correctly using context: . as described.

[crazy-max]

After a few tests, it seems that the generated GitHub Token must be prepended by x-access-token: to be able to authenticate, unlike a PAT which does not need it. Are you aware of this limitation @tonistiigi?

[crazy-max]

@tonistiigi Ok looking at moby/buildkit#1533, buildkit already handles the x-access-token for basic auth through GIT_AUTH_TOKEN. Wonder if the header / secret is properly wired here.

[crazy-max]

Ok got it, we have to use driver-opts: image=moby/buildkit:master in our setup-buildx action. @tonistiigi Like #154 (comment) is it possible for you to update moby/buildkit:buildx-stable-1 image?