Lukas Berger

Apologies for that. This error was caused by a regression in a new release of the builder image, which has been now been rolled back. Please redeploy to restore the...

This is a known issue/working as intended. The Cloud Build config we use to produce these images is [here](https://github.com/GoogleCloudPlatform/buildpacks/blob/main/tools/cloudbuild/create_builder.yaml) and is run on every commit. > Is there a reason...

PHP and Ruby are only supported in the GAE/GCF builders where the runtime is part included in the stack images. We don't have a `runtime` buildpack for either, yet.

You can work around this by specifying `NODE_ENV=development`, which is what npm install does by default and the project seems to assume. The `prepare` script should install devDependencies and then...

Is that with `NODE_ENV=development` or without? Is there an error message printed on startup?

> (btw huge image size compared to my Dockerfile) What base image do you use in your Dockerfile? The run image we use (`gcr.io/buildpacks/gcp/run`) includes few packages and is 111MB...

`gcp-build` has its own buildpack ([source](https://github.com/GoogleCloudPlatform/buildpacks/tree/main/cmd/nodejs/npm_gcp_build)), which is available in App Engine and Cloud Functions. You can override NODE_ENV at build time using `-e NODE_ENV=development` if using `pack` directly or...

`runtime.txt` is not required and in fact not supported. I believe the samples repo has it to support the Heroku builder. We support `.python-version` as well as `GOOGLE_RUNTIME_VERSION` as the...

PHP is supported in App Engine and Cloud Functions. If you use those builders with pack, you should be able to configure them as outlined in the section you linked....

Unfortunately, it's not currently possible to enable caching in Cloud Build when using the `--pack` flag. Builds with this flag invoke the `pack` CLI directly, which only supports local volume...