Josh Dolitsky

rust: build fails if main.rs relocated to src/main.rs

2

Running thew action `chainguard-dev/actions/melange-build@main`: ``` 2022/07/13 22:11:55 melange (hello-server/aarch64): populating workspace /tmp/melange-workspace-833668723 from . 2022/07/13 22:11:55 melange (hello-server/aarch64): -> .gitignore 2022/07/13 22:11:55 melange (hello-server/aarch64): -> Cargo.lock 2022/07/13 22:11:55 melange (hello-server/aarch64):...

Maybe a problem here, or in melange, or most likely in the upstream GitHub actions. Perhaps related to #2 as the workspace does not appear as expected. In the build...

This doesn't cause the build to fail, but also doesn't make me feel good Assumed this would be fixed with the fix of #6 but is not ``` 2022/07/14 21:30:20...

Add a global `--debug` flag which, if set, changes `#!/bin/sh\nset -e` to `#!/bin/sh\nset -x\nset -e` here: https://github.com/chainguard-dev/melange/blob/main/pkg/build/pipeline.go#L212

Ability to package third-party created SBOMs

1

For a Go app, for example, I would like to use something such as [bom](https://github.com/kubernetes-sigs/bom) to generate an SBOM, and package this along with the apk package. Later, in apko,...

Results in error such as ``` 2022/07/05 23:28:50 melange (hello-doc/x86): warning: read |0: file already closed ... Error: failed to build package: unable to run pipeline: exit status 77 2022/07/05...

Allow setup-melange to work when a melange/ directory already exists

1

If using in a repo containing a `melange/` dir, bad stuff happens

What do you want to see in OCI Support?

30

Add comments here with what you would like to see in Helm's OCI support. Please use the :+1: emoji to indicate a upvote for a particular feature, and :-1: to...

Should we build a multiarch image even if only single arch specified?

3

Noticed today, when building an image with an apko yaml like the following: ```yaml contents: ... archs: - x86_64 ``` This produces an image with a manifest like the following...