From owner-freebsd-bugs@freebsd.org Thu Apr 15 07:29:36 2021 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D76B55E2F9E for ; Thu, 15 Apr 2021 07:29:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4FLWFD5ZRZz3GYM for ; Thu, 15 Apr 2021 07:29:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id BF47B5E2F39; Thu, 15 Apr 2021 07:29:36 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BF0755E2CF6 for ; Thu, 15 Apr 2021 07:29:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FLWFD4zTwz3Gbt for ; Thu, 15 Apr 2021 07:29:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 9E1C3518F for ; Thu, 15 Apr 2021 07:29:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 13F7TaKv062497 for ; Thu, 15 Apr 2021 07:29:36 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 13F7TaMC062496 for bugs@FreeBSD.org; Thu, 15 Apr 2021 07:29:36 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 254645] Build and publish official OCI images for FreeBSD releases Date: Thu, 15 Apr 2021 07:29:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: Unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kwiat3k@panic.pl X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Apr 2021 07:29:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D254645 --- Comment #6 from Mateusz Kwiatkowski --- (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 Fre= eBSD developer to be in control of the images. The advantage of going thro= ugh the "Official Images" program is the use of a short name that most of t= he container ecosystem will recognize (for example, "docker pull debian" im= plicitly 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@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 prob= lems 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 defau= lt refuse to launch old images in sake of security and to encourage users to r= un supported versions. > I believe Luca was referring to the image spec [7], which already include= s 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. --=20 You are receiving this mail because: You are the assignee for the bug.=