RFC: Deprecate the use of the Daemon #201
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…he Daemon into the lifecycle Signed-off-by: Juan Bustamante <jbustamante@vmware.com>
|
Maintainers, As you review this RFC please queue up issues to be created using the following commands: Issues(none) |
Signed-off-by: Juan Bustamante <jbustamante@vmware.com>
jjbustamante
force-pushed
the
jjbustamante/feature/deprecate-daemon
branch
from
56b0e67
to
c95da76
Compare
Signed-off-by: Juan Bustamante <jbustamante@vmware.com>
Signed-off-by: Juan Bustamante <jbustamante@vmware.com>
jjbustamante
force-pushed
the
jjbustamante/feature/deprecate-daemon
branch
from
b5b2f08
to
807acc0
Compare
| 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. |
There was a problem hiding this comment.
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>
1 task
|
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Juan Bustamante jbustamante@vmware.com
Readable
Resolves #197