Official example projects use `spec: v0.6`, which now triggers a minimum-version warning

[garysassano]

Environment

• Unikraft CLI 0.4.2 (linux/amd64)

Summary

unikraft build warns that v0.6 is below its supported minimum, but v0.6 is the version used in Unikraft's own published example projects.

Steps to reproduce

Using a Kraftfile copied from a published Unikraft example:

spec: v0.6

name: my-app
runtime: base-compat:latest
rootfs: ./Dockerfile
cmd: ['/usr/bin/bun', 'run', '/usr/src/server.ts']

$ unikraft build ./kernel --output myuser/my-app:latest
Kraftfile spec version is older than minimum; parsing is best-effort min=v0.7 spec=v0.6

Expected

Either the published examples are updated to v0.7, or the compatibility window is documented so users know whether v0.6 remains supported.

Actual

Copying an official example produces a warning that its format is below the minimum and will be parsed "best-effort", with no guidance on what changed in v0.7 or what best-effort might silently get wrong.

Impact

Cosmetic, but it undermines confidence in the examples. Bumping to v0.7 worked with no other changes in my case, which suggests the examples are simply stale.

[danielvallance]

Hello, thanks for the report @garysassano !

I can't see any examples which use 0.6 - and httpserver-bun which you appear to be using uses 0.7 (https://github.com/unikraft-cloud/examples/blob/main/httpserver-bun/Kraftfile)

Have you pulled the latest version of the examples repo?