[anentropic]

Feedback: I think it would be helpful for the KraftCloud docs to link to the Unikraft docs more often where appropriate.

I was skimming around and e.g. https://docs.kraft.cloud/guides/python/#customize-your-appli... shows that besides my app code I need both a Kraftfile and a Dockerfile. Dockerfile is familiar but what is the syntax of Kraftfile?

That page describes it as "the KraftCloud specification" but I could not find such a specification in the KraftCloud docs AFAICT.

I can Google so I found it here: https://unikraft.org/docs/cli/reference/kraftfile/v0.6

I also find myself wondering what are the possible values for "runtime" in the Kraftfile?

The Unikraft docs say they can be OCI images and "Built in to kraft is a reference to our public-access OCI registry which is hosted simply at unikraft.org" https://unikraft.org/docs/cli/packaging#oci-based-packages

...but if I go to unikraft.org it's the marketing+docs homepage for Unikraft.

Is there something like a Unikraft "Hub" site to browse images?

[nderjung]

Hi!

Thanks for the feedback!

Good point on the Kraftfile syntax and as you've seen, there is a reference document. We can make sure to place a link to this in all guides.

The term "KraftCloud Specification" is in fact incorrect, this should just be "`Kraftfile` specification".

We are working on providing a "Unikraft Hub". Since unikraft.org is a public OCI registry and it works through many popular tools like `crane` or `regtool` as well as our native `kraft` CLI tool; you can actually view it locally by running `kraft pkg ls --all --apps --remote`.

Thanks again for the feedback! We'll get on to updating the docs to make these bits clearer!