-
Notifications
You must be signed in to change notification settings - Fork 577
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
Buildpacks: support Dockerfiles #1096
Comments
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
/remove-lifecycle stale (still relevant) |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
/remove-lifecycle stale (still relevant) Upstream tracking issue: buildpacks/rfcs#224 We'd love some help on this one if anyone has interest and bandwidth |
Rotten issues close after 30d of inactivity. /close Send feedback to tektoncd/plumbing. |
@tekton-robot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
CNB RFC 105 introduces the concept of image extensions to the CNB spec. Image extensions output Dockerfiles that can be used to extend build or run-time base images prior to buildpack execution.
Because of the complexity involved, this feature will be implemented using a phased approach (more information can be found buildpacks/rfcs#224). Lifecycle 0.15.0 will have support for phases 1 and 2. Lifecycle 0.17.0 will have support for phase 3.
If this is implemented this should help to close out #1070 (for the 5 phase workflow) - although we may want to duplicate the task since image extensions require experimental features to be enabled, and that may not be desired by all users.
The text was updated successfully, but these errors were encountered: