-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Idea: Add support for OCI layout / deprecate daemon support #197
Labels
Comments
cc: @imjasonh @buildpacks/implementation-maintainers @buildpacks/platform-maintainers |
Assigning this issue to myself for now. |
FYI: @jjbustamante is currently working on a draft of this here: https://hackmd.io/@OYhPqn4pRJ6ixTmFM4vY3w/HkSPjthht |
#203 addresses the first half of this problem, but we will need another RFC at a later date if we want to fully do away with the daemon. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As we integrate further into the cloud native ecosystem, with features like attached SBOMs, cosign etc. daemon is proving to be harder to support. Daemon support has also proven to be hard to support during our BuildKit poc buildpacks/pack#1314 and https://github.com/EricHripko/cnbp
which requires us to reimplement exporter in order to use it with BuildKit. All of these things would be easier if we supported oci image layout instead. GGCR, the core image manipulation library behind lifecycle, already supports loading and saving to oci layout format. Tools like podman support oci layout natively as well.
Given all of the points above, supporting oci layout in favor of daemon seems to make a lot of sense.
We should write out an RFC detailing how this would work while preserving backwards compatibility for tools like pack.
The text was updated successfully, but these errors were encountered: