Skip to content
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

RFC: Deprecate the use of the Daemon #201

Closed
wants to merge 5 commits into from

Conversation

jjbustamante
Copy link
Member

@jjbustamante jjbustamante commented Feb 7, 2022

Signed-off-by: Juan Bustamante jbustamante@vmware.com

Readable

Resolves #197

…he Daemon into the lifecycle

Signed-off-by: Juan Bustamante <jbustamante@vmware.com>
@buildpack-bot
Copy link
Member

Maintainers,

As you review this RFC please queue up issues to be created using the following commands:

/queue-issue <repo> "<title>" [labels]...
/unqueue-issue <uid>

Issues

(none)

Signed-off-by: Juan Bustamante <jbustamante@vmware.com>
@jjbustamante jjbustamante force-pushed the jjbustamante/feature/deprecate-daemon branch from 56b0e67 to c95da76 Compare February 8, 2022 21:17
Signed-off-by: Juan Bustamante <jbustamante@vmware.com>
Signed-off-by: Juan Bustamante <jbustamante@vmware.com>
@jjbustamante jjbustamante force-pushed the jjbustamante/feature/deprecate-daemon branch from b5b2f08 to 807acc0 Compare February 10, 2022 20:07
For example: The OCI image specification defines a Manifest file but in the Daemon this concept doesn't exists or if we try to add [annotations](https://github.com/buildpacks/rfcs/pull/196) then we can't guarantee the same behavior with images saved in the Daemon.


The main goal is to deprecate the use of the Daemon in the lifecycle, embrace the use of the [OCI specification](https://github.com/opencontainers/image-spec) and move the complexity of interacting with the Daemon into the **Platform** component.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be helpful to list out all the benefits that we hope to achieve. I can recall -

  • The ability to generate a manifest for local images
  • Removing complexity from the lifecycle
  • Giving end users the ability to export a tarball
  • (Maybe) making it easier to support BuildKit

I think we need to decide which goals are most important and which are out of scope to make a decision around how to proceed.

Signed-off-by: Juan Bustamante <jbustamante@vmware.com>
@jjbustamante
Copy link
Member Author

I am closing this RFC, the scope was probably too ambitious and we didn't get any resource from the Google Summer of Code to work in the Proof Of Concept. On the other hand, there is another RFC on draft state #203. I hope to move forward with that one because the feature to export to OCI is one of the options to reach the goal of removing the Daemon support

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

Successfully merging this pull request may close these issues.

Idea: Add support for OCI layout / deprecate daemon support
3 participants