Till!

 From your readme **on this repository**, the instructions. This is what I followed. My database works, I suspect from the pr you linked the automated postgres setup is not...

Yes, that's fine, and I get it, but then update the readme. That's why I created this issue. The problem that remains is, why is your schema job not working...

Just wanted to add, I realize the error is also a PICNIC (me!), but I still think that pack should not allow this.

Just to avoid mis-understandings: The build that fails is running on `linux/amd64`. I realize now that my `pack report` output is from local — but it is the same version...

I found the offenders: ```sh tar -tzf ./temp-image/ccb10c19592c9cd4efbf40ec2a35d433a11d3e626f9376583f19e6da53477492 | sort | uniq -c | awk '$1 > 1 {print $1, $2}' | head -20 2 /cnb/buildpacks/paketo-buildpacks_ca-certificates/3.10.3 2 /cnb/buildpacks/paketo-buildpacks_ca-certificates/3.10.3/LICENSE 2 /cnb/buildpacks/paketo-buildpacks_ca-certificates/3.10.3/NOTICE...

I can re-run my build and it will eventually produce a builder that works.

So for local builds to test/debug my setup I just can't without publish going through a registry?

> Just for reference, you mentioned > > > Over the weekend, I had a weird error: > > I am not 100% sure, but maybe this error was a...

For the record: I currently don't need an arm64 build for production. I wanted to run what we run in CI (because the feedback loop is cumbersome) on my m3...

This is really enlightening! Thank you, @jjbustamante I am guessing buildx would be the way to go, but also what you're saying is that I could use `--publish` and build...