[Bug 254645] Build and publish official OCI images for FreeBSD releases

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254645

--- Comment #3 from Mateusz Kwiatkowski <kwiat3k at panic.pl> ---
(In reply to Luca Pizzamiglio from comment #2)
Hi Luca,

Thank you for questions.

> * I'm using skopeo to download docker images and convert them to OCI format. How did you configured the storage driver in etc/containers/storage.conf
> AFAIK, zfs is supported (it would be ideal), but it would work only for root

This storage configuration matters in runtime context. I only briefly played
with containerd with nullfs snapshotter. For more runtime details I'd refer to
great Samuel's work: https://github.com/samuelkarp/runj

> * one important information that FreeBSD OCI images should have is the os.version, to enforce proper check on jails and host messages. Do you think os.version (in the manifest field of index.json) is a suitable place or it would be better to adopt a custom annotation?

Yes, we can put whatever is needed for runtime to validate images. I created
minimal draft of runtime spec for FreeBSD for my needs:
https://github.com/runhyve/umoci/commit/759dccf4cbbe47a54ca2ef3d44d9c3eb83d7a157
And Samuel made his own draft:
https://github.com/samuelkarp/runj/blob/main/runtimespec/config.go

I think that these specs would grow and stabilize over time and in the future
they should be submitted as official OCI spec:
https://github.com/opencontainers/runtime-spec/blob/master/specs-go/config.go

os.version in particular could land in FreeBSD specific subtree of schema.
Here's example for Solaris:
https://github.com/opencontainers/runtime-spec/blob/master/schema/config-solaris.json

-- 
You are receiving this mail because:
You are the assignee for the bug.