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
Hi,
I am here to introduce and propose our image service - Nydus which is aiming at boosting container startup. Briefly speaking, Nydus splits an OCI image into data and metadata parts with additional rich features, which are stored in registry complying to OCI distribution spec. To mitigate the pressure of registry, Nydus has an option to fetch data(blob) from p2p infra in priority. We already provide the ability to integrate Nydus with Dragonfly from Alibaba. But in order to provide users more options and enlarge the usability of Nydus, we are thinking about also integrate Nydus with Kraken.
Nydus storage backend reads data from docker registry or p2p cluster/infra via registry HTTP API, from which only demanded data will be pulled. So a ranged pull is required by Nydus.
So does this interest Kraken community?
Do we have something more to discuss about?
The text was updated successfully, but these errors were encountered:
Hi,
I am here to introduce and propose our image service - Nydus which is aiming at boosting container startup. Briefly speaking, Nydus splits an OCI image into data and metadata parts with additional rich features, which are stored in registry complying to OCI distribution spec. To mitigate the pressure of registry, Nydus has an option to fetch data(blob) from p2p infra in priority. We already provide the ability to integrate Nydus with Dragonfly from Alibaba. But in order to provide users more options and enlarge the usability of Nydus, we are thinking about also integrate Nydus with Kraken.
Nydus storage backend reads data from docker registry or p2p cluster/infra via registry HTTP API, from which only demanded data will be pulled. So a ranged pull is required by Nydus.
So does this interest Kraken community?
Do we have something more to discuss about?
The text was updated successfully, but these errors were encountered: