`pack build` segfaults on M2 mac + podman about pack HOT 6 CLOSED

Using Docker Desktop or Colima, it works

from pack.

Hi @mpern.

But it looks like it is a problem with our sample ruby buildpack on ARM

from pack.

There are some documentation around some buildpacks and builders available for ARM arquitectura, like the one from Daniel or Dshaun you can give it a try also.

from pack.

I don't think it's the buildpack.

After switching to colima to manage my docker runtime, it "just works"

> colima start --cpu 4 --memory 16
> export DOCKER_DEFAULT_PLATFORM=linux/amd64
> pack build sample-app -p sample/apps/ruby-bundler/ -B cnbs/sample-builder:jammy
...
[exporter] *** Images (df1f75d8e38e):
[exporter]       sample-app
[exporter] Timer: Saving sample-app... ran for 128.743222ms and ended at 2024-03-15T10:20:37Z
[exporter] Timer: Exporter ran for 875.31219ms and ended at 2024-03-15T10:20:37Z
[exporter] Timer: Cache started at 2024-03-15T10:20:37Z
[exporter] Reusing cache layer 'samples/ruby-bundler:bundler'
[exporter] Timer: Cache ran for 1.894101ms and ended at 2024-03-15T10:20:37Z
Successfully built image sample-app

from pack.

DOCKER_DEFAULT_PLATFORM=linux/amd64

I think, because you are setting your platform to be linux/amd64, we are working to support arm architecture, but today it is limited.

from pack.

the thing is, you are trying to use the sample builder cnbs/sample-builder:jammy, this builder is based on jammy linux/amd64, also the ruby buildpack is probably pointing to linux/amd64 binaries, then when you try to run that on linux/arm you get into issues, because you need a builder/buildpacks that are compliant for arm architecture. This is a known issue, and we are working on that direction. (see this RFC).

That's why I suggested to try to use the builders from Daniel or DShaun because they already did the job to compile, some of them, for arm architecture.

If you run pack build and you uses a compliant arm builder and buildpacks, you should be able to get your app image built correctly

from pack.