All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Stefan Agner <stefan@agner.ch>, <meta-virtualization@yoctoproject.org>
Cc: Brandon Shibley <brandon.shibley@toradex.com>
Subject: Re: OpenEmbedded Image Format
Date: Mon, 10 Sep 2018 20:34:12 -0400	[thread overview]
Message-ID: <8d25ae3a-6f8a-7b45-33e0-1564dce82eb2@windriver.com> (raw)
In-Reply-To: <a9421b92abcdbc3c76f9bd6783cc0c5a@agner.ch>

On 2018-09-10 7:21 PM, Stefan Agner wrote:
> Hi,
> 
> Is there a OpenEmbedded image type which allows to build images which
> are OCI Image Format compliant? meta-virtualization includes the
> oci-image-tools, hence the recipe for tooling is there. There is
> currently no -native support for oci-image-tool and its dependencies,
> but I guess that shouldn't be too far away. Any thoughts?

This is something that we typically do with umoci, not with the
raw tools.

re-inventing what better tools already do in a bbclass using
the raw oci-image-tools is an not an exercise worth doing.

Not to mention, nearly every use case I currently have for
working with container images, involves registries, and adding
something as clunky as a build system to generate the images
just doesn't make sense.

How were you planning on running/using the OCI bundles ?

I've been doing similar things for quite some time in meta-cube
i.e. http://layers.openembedded.org/layerindex/recipe/87474/

But that all happens outside of the build system.

I could move more of the tools over to meta-virt, if there's
interest.

Cheers,

Bruce

> 
> --
> Stefan
> 



  reply	other threads:[~2018-09-11  0:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-10 23:21 OpenEmbedded Image Format Stefan Agner
2018-09-11  0:34 ` Bruce Ashfield [this message]
2018-09-11  1:01   ` Stefan Agner
2018-09-11  1:10     ` Bruce Ashfield
2018-09-11  4:37       ` Stefan Agner
2018-09-11 11:14         ` Bruce Ashfield
2018-09-11 17:01           ` Stefan Agner
2018-09-11 17:19             ` Bruce Ashfield
2018-10-04 13:29             ` Bruce Ashfield

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8d25ae3a-6f8a-7b45-33e0-1564dce82eb2@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=brandon.shibley@toradex.com \
    --cc=meta-virtualization@yoctoproject.org \
    --cc=stefan@agner.ch \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.