[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 #6 from Mateusz Kwiatkowski <kwiat3k at panic.pl> ---
(In reply to Samuel Karp from comment #5)
> Docker, Inc. sponsors an "Official Images" program that publishes images to Docker Hub.  The program is managed on GitHub [1] and would enable a FreeBSD developer to be in control of the images.  The advantage of going through the "Official Images" program is the use of a short name that most of the container ecosystem will recognize (for example, "docker pull debian" implicitly pulls the "Official Image" of Debian located at docker.io/library/debian [2]; FreeBSD could have the "freebsd" short name).

That's what I'm thinking about as a long term goal of OCI at FreeBSD project. I
think that for that matter core team should be engaged. Ed is already
subscribing this issue so let's wait for his input.


> I'm still new to FreeBSD, so my apologies for asking a stupid question.  Is there a requirement that a FreeBSD userland program is built to run on a particular version of FreeBSD?  Do the kernel or syscall interfaces change between versions?

I have been running jails with base systems lagging several major versions
behind host system and 99% of software was working fine. I only recall problems
with network related apps from base like netstat, sockstat - there were
probably some struct changes. Backwards compatibility is one of FreeBSD's
selling points but I think that spec should include os.version and by default
refuse to launch old images in sake of security and to encourage users to run
supported versions.


> I believe Luca was referring to the image spec [7], which already includes os.version in the index platform object.  I'm generating OCI images [8], but not currently including os.version.

Ok, I agree. I'll add it to my images.


> For the runtime config, agreed!  I'd be happy to collaborate on this with you.

I think I already asked on Github, but I'll repeat. :-) What do you think on
creating #freebsd channel in OCI Slack? We can also have #freebsd-oci on
freenode if you prefer IRC.

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