You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Simplifying the ability for Concourse to use a container image to build other container images utilizing Prototypes as opposed to the OCI Build Task.
Problem
Currently, the oci-build-task is a container image that is meant to be used in a Concourse task to build other container images.
The process to build an OCI image from its Dockerfile and push that image to a registry involves quite a lot of steps and can be verbose and complicated
Proposed Solution
Utilize Prototypes instead! Given that prototypes is built off the back of resources, it should be an easier abstraction to reason about.
Outcomes
OCI images become easier to build and push
Users are provided the same flexibility and power, but in an easier to manage format
TLDR
Problem
oci-build-task
is a container image that is meant to be used in a Concourse task to build other container images.Proposed Solution
Outcomes
Current Status
References
#6540 - Add support for prototypes
See: Reinventing Resource Types
The text was updated successfully, but these errors were encountered: