From nobody Mon Oct 9 15:19:04 2023 X-Original-To: freebsd-net@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4S42kZ1RNfz4wpHL for ; Mon, 9 Oct 2023 15:19:18 +0000 (UTC) (envelope-from dfr@rabson.org) Received: from mail-yw1-x112e.google.com (mail-yw1-x112e.google.com [IPv6:2607:f8b0:4864:20::112e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4S42kY6J5cz3NFL for ; Mon, 9 Oct 2023 15:19:17 +0000 (UTC) (envelope-from dfr@rabson.org) Authentication-Results: mx1.freebsd.org; none Received: by mail-yw1-x112e.google.com with SMTP id 00721157ae682-5a7ac4c3666so4119397b3.3 for ; Mon, 09 Oct 2023 08:19:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rabson-org.20230601.gappssmtp.com; s=20230601; t=1696864755; x=1697469555; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=lYeUZnSdepv6C+9UCzSYe3L3golRJSTcZu5RGVQO2xE=; b=3avKLraK6KocVCUXRha5kk0vwu1fXCaPVUnWRStHUrWCAyX4rNUVGcO6rYQMiHgqDD 37tz6kJCVjARJU4XOJ7i9bFtBKt0by9DThfOLQiERAMekMVkZkAc0kesHhWPPQIIW6rf l5gXCOMlSZ/kiTNYmAo+0VT08oV99XP/+U57KmHEG2O2wZFwt0UKSKFw3TCT/d2fBuyJ rMoW9nvfFMOzoNh9L0+bRecjKGFa2c3U4XQCut55R4RBYqzgDVGj9UPQ9ogYwf56bwX6 LehLnV5sjmaXqtwUtqw25Ay9BdvCYpSuoBREi4JRoBXmLVPiOCS6db1u7dtgtNPHW2BT NM2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696864755; x=1697469555; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=lYeUZnSdepv6C+9UCzSYe3L3golRJSTcZu5RGVQO2xE=; b=g8i4lfbb+se+EJ+1+LyMKexZuXUOlu1yiohFXdqZhygWiNiG0bewNStDjILWwytAn5 G2AP6g3gotdv4T8xBgSFkZPHvincEDlDEOTxhOa+K/SInJAtX1+0uBRt+y4/KN0tYxRX qypRRQnsNOto3WGylxtM6a8RIYaK1bG6u9UREQFJXXbuYjYXW1ANU3rreDPpRylqz0UW HARo6S6eFQyxVRT7TuYP+1WWfrDBtapD/+Oezf3bM9HZHhGXTnqXUDjstQag6kegbAs8 Uwbmf0ySpZsXhc39CyJFX92sWlOfRriCO3ektRmCTilkKw/c6z59BQ1KDMy5uQn4x0+3 uuTQ== X-Gm-Message-State: AOJu0Yz03LaQ4dMZbEvQuJ1LWjDkcWTJvxHC+gujZZTwrE1vc4c/nCtp J8MScQw+5uqOn8X4TxdpX8ZRQULzGk1x8oCci5IjZ+/MHg6Kr3EkBMWuWw== X-Google-Smtp-Source: AGHT+IEmUdqDMy335TJ7/CXip8fDe5q67NgxS/Xv/2rJ72e2appYRhxZ7K/xlkQpcGY7j5t+LKU57ZouQF3XYsdJKU8= X-Received: by 2002:a81:8104:0:b0:59b:bacb:a84f with SMTP id r4-20020a818104000000b0059bbacba84fmr17013775ywf.47.1696864755429; Mon, 09 Oct 2023 08:19:15 -0700 (PDT) List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Doug Rabson Date: Mon, 9 Oct 2023 16:19:04 +0100 Message-ID: Subject: Re: OCI image compatibility spec - FYI To: Greg Wallace Cc: freebsd-net@freebsd.org Content-Type: multipart/alternative; boundary="000000000000face2106074a1c02" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4S42kY6J5cz3NFL --000000000000face2106074a1c02 Content-Type: text/plain; charset="UTF-8" On Mon, 9 Oct 2023 at 13:51, Greg Wallace wrote: > Hi all, > > I have been trying to stay tuned in to all the efforts to get a native OCI > runtime on FreeBSD. There are a lot of people interested in this and > several efforts underway. > > In the course of listening in on some of the OCI community developer > calls, I learned about this effort to create image compatibility > specification > > https://github.com/opencontainers/tob/pull/128 > > I asked if they planned to include FreeBSD as a supported platform and > they have been very open to the idea but they need FreeBSD developers to > express interest and get involved. > > If this interests you, you can jump into the PR or ping me and I'd be > happy to connect with the engineers heading this up. > I am very interested in the area of adding FreeBSD extensions to the OCI specification(s). Your PR covers the image spec - I actually think that it might be better to start trying to define a FreeBSD extension for the runtime spec. Doug. > --000000000000face2106074a1c02 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable



On Mon, 9 Oct 2023 a= t 13:51, Greg Wallace <gre= g@freebsdfoundation.org> wrote:
Hi all,

I have been trying to stay t= uned in to all the efforts to get a native OCI runtime on FreeBSD. There ar= e a lot of people interested in this and several efforts underway.

In the course of listening in on some of the OCI community= developer calls, I learned about this effort=C2=A0to create image compatib= ility specification


I asked if they planned= to include FreeBSD as a supported platform and they have been very open to= the idea but they need FreeBSD developers to express interest and get invo= lved.

If this interests you, you can jump into the= PR or ping me and I'd be happy to connect with the engineers heading t= his up.

I am very interested in= the area of adding FreeBSD extensions to the OCI specification(s). Your PR= covers the image spec - I actually think that it might be better to start = trying to define a FreeBSD extension for the runtime spec.

Doug.
=C2=A0
--000000000000face2106074a1c02--