Crypto is Not Defined Error

[danielcrabtree]

Contributing guidelines

• I've read the contributing guidelines and wholeheartedly agree

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

v3.7.0 gives ::error::crypto is not defined, rolling back to v3.6.1 resolves the issue.

Expected behaviour

v3.7.0 works without any errors.

Actual behaviour

v3.7.0 gives ::error::crypto is not defined.

Repository URL

No response

Workflow run URL

No response

YAML workflow

name: "Deploy Latest"

on:
  push:
    branches: ["develop"]

jobs:
  docker:
    runs-on: ubuntu-latest
    steps:     
      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v3
        with:
          config-inline: |
            [registry."docker-registry:5000"]
              http = true
              insecure = true

Workflow logs

No response

BuildKit logs

No response

Additional info

No response

[pandalec]

Thank you! This drove me crazy. Tried to switch a (working) dind setup from non-TLS to TLS and I always ran into this issue. Downgrading to 3.6.1 finally did it!

[crazy-max]

Hum maybe on some runners Node.js is built without including support for the node:crypto module: https://nodejs.org/docs/latest-v18.x/api/crypto.html#determining-if-crypto-support-is-unavailable

I will revert this change for now