Skip to content
This repository has been archived by the owner on Feb 23, 2024. It is now read-only.

Provenance for images built with other tooling #4

Open
jeremyrickard opened this issue Sep 22, 2022 · 0 comments
Open

Provenance for images built with other tooling #4

jeremyrickard opened this issue Sep 22, 2022 · 0 comments

Comments

@jeremyrickard
Copy link
Member

There is a brief mention of non Dockerfile driven workflows with the buildType attribute, but there aren't any examples or narrative that explain how we expect this to work for non Dockerfile based things (i.e. Bazel, or cloud native build packs, or ko or other things that simply create a tgz of a layer and either append to an existing thing or build an entirely new manifest around it).

Is the initial scope for this going to be strictly limited to things in the realm of Buildkit / Dockerfile? Are there any important use cases within Azure services that would get missed by that assumption?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant