Add Daemon support into pack

[jjbustamante]

Description

As a Developer, I want to use Pack to build a container image from my application source code and save it into the Daemon when the flag --publish is missing.

Currently, the previous statement works, but the Lifecycle interacts directly with the Daemon, we are working on different approaches to remove the Daemon support in the Lifecycle, in all scenarios, Pack is assuming the responsibility of dealing with the Daemon. The intention of this issue is to work in a Proof of concept for this new interaction.

Proposed solution

The idea is to work on exposing some kind of OCI Registry (the API) server in Pack. Pack must prepare and configure to have network communication with this API and execute the lifecycle to use it as the source/sink of images.

This OCI Registry exposes by Pack must "translate" the requests from the Lifecycle and somehow convert them into Daemon's request (and vice versa).

Describe alternatives you've considered

Many other alternatives as described in the RFC

Additional context

• This feature should be documented somewhere

[jromero]

Setting status to blocked, since this issue was submitted to Google Summer of Code. This is scheduled to be worked on by a mentee.

[viveksahu26]

Hey @jromero , I want to work as a Mentee for this issue. As I am also new to this project. So, I need a Mentor to be assigned throughout this project, similar to mentorship program. What's your thoughts?

[jjbustamante]

I am closing this one as we already implemented a feature to export to OCI layout format on disk, and the PoC to try to remove the daemon demonstrate a very bad performance using this option