GitHub actions custom image - process did not complete successfully exit code 1

[dim plover]

Hello! Did anybody face the issue of using a custom docker image in GitHub actions? I'm getting process "cat LICENSE" did not complete successfully: exit code: 1 when trying to use exact copy of python:3.11-alpine image. When it gets executed using python:3.11-alpine itself, it works fine. Locally this pipeline also works fine.

Logs can be found here: https://github.com/KernelPryanic/dagger-sample-pipeline/actions/runs/3557574239/jobs/5975668336
Pipeline: https://github.com/KernelPryanic/dagger-sample-pipeline/blob/7a9679929c8e7ea41ab656215d884897dda32ebd/pipeline.py
Dockerfile: https://github.com/KernelPryanic/dagger-sample-pipeline/blob/7a9679929c8e7ea41ab656215d884897dda32ebd/Dockerfile

GitHub actions custom image - process did not complete successfully exit code 1

[waxen crypt]

Hi, check your version. Latest v0.2.0 has some breaking changes.

[dim plover]

Hey @waxen crypt , that was the first thing I thought about, but later I narrowed the failure and found out that it's connected to the custom docker image I use. I've attached the link to the Dockerfile for the image, it's basically a copy of python:3.11-alpine

[fierce hamlet]

👋 looks like the image you're trying to use has been pushed with an arm64 architecture, and github runners currently don't support it.

If you push your image with amd64 that should fix it:

manifest-tool inspect ghcr.io/kernelpryanic/dagger-debug:latest
Name: ghcr.io/kernelpryanic/dagger-debug:latest (Type: application/vnd.docker.distribution.manifest.v2+json)
      Digest: sha256:c0852bb962aa9fd8ff681629c2f4d17368bc01e13d4325febbfde9af579d1d87
        Size: 1368
          OS: linux
        Arch: arm64
    # Layers: 5
      layer 01: digest = sha256:6875df1f535433e5affe18ecfde9acb7950ab5f76887980ff06c5cdd48cf98f4
      layer 02: digest = sha256:e190eeb0612a6514b857c64886ec8f64d8e235210be5682cf6abbc5bd172b135
      layer 03: digest = sha256:b4727b51eed627eface71c55490f3017153992b7d9ae395a99b1e11841128d06
      layer 04: digest = sha256:ce34a3004b391575b577e7922f6d501a0b8ba079dc0741b068b86558c26ee4a1
      layer 05: digest = sha256:86c270266b6f1942f4120af4ec7278184a61adb708209c33c2320154d82f8a31

same thing happens if you're trying to use it with a regular docker run