Quickstart instruction doesn't work for me

[theyoprst]

skaffold dev cannot build an image:

...
Digest: sha256:42e2ea1eec79c769a4c301cbb3536890d8d3860effde4034d8c6fc57f93f9587
Status: Downloaded newer image for buildpacksio/lifecycle:0.17.7
===> ANALYZING
[analyzer] Timer: Analyzer started at 2025-02-09T18:12:27Z
[analyzer] Image with name "skaffold-buildpacks-node:latest" not found
[analyzer] Timer: Analyzer ran for 424.329µs and ended at 2025-02-09T18:12:27Z
===> DETECTING
[detector] Timer: Detector started at 2025-02-09T18:12:27Z
[detector] 3 of 5 buildpacks participating
[detector] google.nodejs.runtime    1.0.0
[detector] google.nodejs.npm        1.1.0
[detector] google.utils.label-image 0.0.2
[detector] Timer: Detector ran for 981.517686ms and ended at 2025-02-09T18:12:28Z
[detector] ERROR: failed to write buildpack group: open /layers/group.toml: permission denied
Cleaning up...
 - No resources found
build [skaffold-buildpacks-node] failed: executing lifecycle: failed with status code: 1

My environment: OS X arm64, Orbstack (as a Docker Desktop replacement). Tried both in minikube and kind, same result.

Tried to search, find a similar discission in the buildpacks project: buildpacks/community#219

[santhanam87]

Any solutions to this ? I am also stuck on the same problem.

[oheeg]

I have the same issue and am looking for solutions

[Aaur1s]

Specify trustBuilder: true in buildpacks section (or avoid buildpacks). Fixes for me on Windows

[petarmihaylov]

Specify trustBuilder: true in buildpacks section (or avoid buildpacks). Fixes for me on Windows

Please forgive the ignorance, but what are the implications of trusting the builder? Sounds like if it defaults to false there is probably a good reason for it.

[Aaur1s]

trustBuilder: true tells skaffold that buildpack image and it's building process is safe, it's completely fine to me to use it on google default buildpacks from gcr.io. By default, skaffold sets trustBuilder to false because there are inherent security risks (for example, you could accidentally pull malicious code from a compromised builder).

[ruigulala]

Omg, thanks @Aaur1s ! This saved my day!

[mike-obas]

Specify trustBuilder: true in buildpacks section (or avoid buildpacks). Fixes for me on Windows

I am having this issue on MacOs and the solution does not work for me. Do you have any other solution that could help?

[nnWhisperer]

I think, this issue must be prioritized, obviously many first-timers of the tool struggle with it - seeing the tool broke 2 min into using it and setting up an unsafe way to proceed doesn't talk good about the tool/project.

[jamesa-unito]

Having the same issue. Setting trustBuilder: true did not resolve the problem.

[jamesa-unito]

So, just a correction. The gcr.io/buildpacks/builder:v1 pack builder does not support linux/arm64 platform. I am building locally on Apple Silicone.

This is a working configuration to get the hello world to start:

apiVersion: skaffold/v4beta13
kind: Config
metadata:
  name: buildpacks-node-tutorial
build:
  artifacts:
    - image: skaffold-buildpacks-node
      buildpacks:
        builder: paketobuildpacks/builder:base
        trustBuilder: true
manifests:
  rawYaml:
    - k8s/web.yaml

Is there a better best practice that allows me to use the Google provided builder on this architecture?