-
Notifications
You must be signed in to change notification settings - Fork 160
ERROR: pack build
with google-22
builder fails detection on Apple M1 Pro/Max
#500
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I have exactly the same error on Mac Air M1 as a temp workaround I'm building with previous buildpack version |
This resolved the issue for me, otherwise same issue on an M3 Max. Last worked a month ago, now getting the exact error as above. |
Same issue on M4 Max. |
The error in detection is the same for the current |
Same issue on Linux |
Same issue on Mac M1 Pro - workaround from @steals helped |
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
The
pack build
command fails with the error "ERROR: No buildpack groups passed detection." when using thegcr.io/buildpacks/builder:google-22
builder image on Apple M1 Pro and M1 Max machines. This issue started occurring after the latest push of thegoogle-22
image. The same command works on Ubuntu.Additional context
How are you using GCP buildpacks?
pack
and thegcr.io/buildpacks/builder
Did this used to work?
Yes. This was working before the latest update to the
gcr.io/buildpacks/builder:google-22
image. The issue started occurring yesterday (April 14, 2025).What language is your project primarily written in?
Javascript/Typescript - nodejs runtime
Steps To Reproduce
Steps to reproduce the behavior:
pack
CLI installed.pack build --builder=gcr.io/buildpacks/builder:google-22 test --verbose
on an Apple M1 Pro or M1 Max machine.Expected behavior
The
pack build
command should successfully detect buildpacks and proceed with the build process, resulting in a container image.Actual behavior
The
pack build
command fails during the detection phase with the following error:The text was updated successfully, but these errors were encountered: