Date: Mon, 29 Mar 2021 20:37:44 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 254645] Build and publish official OCI images for FreeBSD releases Message-ID: <bug-254645-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D254645 Bug ID: 254645 Summary: Build and publish official OCI images for FreeBSD releases Product: Base System Version: Unspecified Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: bugs@FreeBSD.org Reporter: kwiat3k@panic.pl Hello, I wanted to start discussion about providing official OCI images by FreeBSD project and publishing them in one of public registries (eg. Docker HUB). I am observing growing interest in OCI standard among FreeBSD community. It= 's now possible to build and launch containerd on FreeBSD [1][2], native runti= me is in work [3] and I have fixed FreeBSD support in umoci [4] and skopeo [5] tools. Containerd, when used with nerdctl [6] could become complete docker replacement on FreeBSD. I think that images should be build during the release process just as AWS' AMIs are. I documented build process here: https://gitlab.com/runhyve/jailer/-/snippets/2089767 And here is instruction how to create jail out of OCI pulled directly from Docker HUB: https://gitlab.com/runhyve/jailer/-/snippets/2082864 [1] https://github.com/containerd/containerd/commit/b624486c84c3940fde5ef20ca10= 89f92f9d62254 [2] https://github.com/containerd/containerd/pull/4858 [3] https://github.com/samuelkarp/runj [4] https://github.com/opencontainers/umoci [5] https://github.com/containers/skopeo [6] https://github.com/containerd/nerdctl --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-254645-227>