docker / build-push-action

GitHub Action to build and push Docker images with Buildx
https://github.com/marketplace/actions/build-and-push-docker-images
Apache License 2.0
4.11k stars 527 forks source link

ERROR: failed to solve: process "/bin/sh -c #1008

Closed yellowbean closed 7 months ago

yellowbean commented 7 months ago

Contributing guidelines

I've found a bug, and:

Description

Suddenly build failed, but I didn't change anything about the workfile.

with same workflow file , it was a successful build on Build 86 but somehow failed at Build 87

Screenshot 2023-11-18 at 11 55 38

I can build successfully on my local.

Expected behaviour

The workflow file should be run successfully

Actual behaviour

it raise error :

buildx failed with: ERROR: failed to solve: process "/bin/sh -c cd /opt/build && stack build --copy-bins --local-bin-path /opt/build --resolver lts-18.22 # --system-ghc" did not complete successfully: exit code: 1

Repository URL

https://github.com/yellowbean/Hastructure/

Workflow run URL

https://github.com/yellowbean/Hastructure/actions/runs/6814113581

YAML workflow

https://github.com/yellowbean/Hastructure/actions/runs/6814113581/workflow

Workflow logs

No response

BuildKit logs

No response

Additional info

No response

crazy-max commented 7 months ago

Looking at the logs, I think this is an issue within your project and not the action or Buildx/BuildKit: https://github.com/yellowbean/Hastructure/actions/runs/6814113581/job/18754144029#step:6:6090

#12 935.9 Preprocessing executable 'Hastructure-exe' for Hastructure-0.20.2..
#12 935.9 Cabal-simple_mPHDZzAJ_3.2.1.0_ghc-8.10.7: can't find source for FormBuilder in
#12 935.9 app,
#12 935.9 .stack-work/dist/x86_64-linux/Cabal-3.2.1.0/build/Hastructure-exe/autogen,
#12 935.9 .stack-work/dist/x86_64-linux/Cabal-3.2.1.0/build/global-autogen

Might be related to this change: https://github.com/yellowbean/Hastructure/compare/v0.22.5...v0.22.6#diff-0e14c027a17482b517041329a3ae4e7237fa7e8e6f303c3d6eda2c58aa29cee6R95

yellowbean commented 7 months ago

@crazy-max Thank you very much on pin point to the root issue