error: could not create a builder instance with TLS data loaded from environment

[lexfrei]

Behaviour

Steps to reproduce this issue

1. Install k3s in your arm64 cluster
2. Install actions-runner-controller
3. Run your workflow there

Expected behaviour

No errors

Actual behaviour

error: could not create a builder instance with TLS data loaded from environment. Please use docker context create <context-name> to create a context for current environment and then create a builder instance with docker buildx create <context-name>

Configuration

• Repository URL (if public): https://github.com/lexfrei/vk2tg/tree/6b67c17cf095a7147a40db4023f2121fd1cb1d9a

• Build URL (if public): https://github.com/lexfrei/vk2tg/runs/3424244864?check_suite_focus=true#step:5:96

name: Main Workflow

on:
  push

jobs:
  lint:
    runs-on: self-hosted
    steps:
      - uses: actions/[email protected]
      - name: golangci-lint
        uses: golangci/[email protected]
        with:
          version: v1.42
      # Waiting for https://github.com/hadolint/hadolint-action/issues/38
      # - name: hadolint
      #   uses: hadolint/[email protected]
      #   with:
      #     dockerfile: build/vk2tg/Dockerfile

  build:
    needs: lint
    runs-on: self-hosted
    steps:

    - name: Docker meta
      id: docker_meta
      uses: docker/[email protected]
      with:
        images: ghcr.io/${{ github.repository }}
        flavor: |
          latest=true
        tags: |
            type=ref,event=branch
            type=ref,event=pr
            type=sha
    - name: Set up QEMU
      uses: docker/[email protected]

    - name: Checkout
      uses: actions/[email protected]

    - name: Set up Docker Buildx
      uses: docker/[email protected]

  <...>

Logs

logs_415.zip

[crazy-max]

@lexfrei Looks like you're using a self-hosted runner and the default context is from a tls environment but you can't create a builder instance from a tls environment (see docker/buildx#30)

You have to create a context for the current environment with docker context create <context-name> like the error message suggest.

[lexfrei]

For history:
Fix

[DmitriyBobrovskiy]

For history: Fix

For the history if repo will be gone:

[joaoluiznaufel]

but this is coming back to version 1. Someome already know how to do a proper fix using v2?

[joaoluiznaufel]

ah, found it, you can use the v2 that it will continue work

[lifeofmoo]

For history: Fix

For the history if repo will be gone:

Hello, I used the findings above to resolve the issue for me.

#311

Is anyone able to comment/shed light as to WHY this works. Is this is an accepted approach or a workaround?

[crazy-max]

For history: Fix

Made some changes in #341 to automatically create a docker context if TLS data are loaded for default context if someone is willing to test on his self-hosted environment 🙏:

      -
        name: Set up Docker Buildx
        uses: crazy-max/docker-setup-buildx-action@docker-context-tls

[crazy-max]

Should be fixed since 3.6.0