Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build story: producing an OCI image #396

Closed
TomasTomecek opened this issue Oct 19, 2016 · 9 comments
Closed

Build story: producing an OCI image #396

TomasTomecek opened this issue Oct 19, 2016 · 9 comments

Comments

@TomasTomecek
Copy link

The image spec is really awesome and I can't wait to see a stable release of the spec, integrated everywhere.

What I'm personally missing right now is a way to produce (build, compose, orchestrate; name it the way you want) an image: I mean a spec for steps needed to create an image. I'm sure that's very much out of scope of this project. What I'm interested in is

  1. if such spec will ever be part of OCI
  2. or if there are any plans in this area
  3. or if this topic is really up to vendors to deal with

I really would like to know @vbatts' ideas about this.

@amitsaha
Copy link
Contributor

You can learn a bit more about it here #126

@TomasTomecek
Copy link
Author

@amitsaha thanks for the link! I think that this issue goes even one step further: it's not just about implementing the spec, it's also about producing images valid in this spec.

@wking
Copy link
Contributor

wking commented Oct 19, 2016

On Tue, Oct 18, 2016 at 11:43:49PM -0700, Tomas Tomecek wrote:

What I'm personally missing right now is a way to produce (build,
compose, orchestrate; name it the way you want) an image: I mean a
spec for steps needed to create an image.

I'm not sure if @cyphar is actively maintaining it (he's getting
pulled in quite a few directions at the moment ;), but there's also
1.

I've also posted a rough sketch 2 using the API that's in flight in
opencontainers/image-tools#5. I haven't kept that sketch up to date
with recent image-tools changes, but the basic idea still applies.

And the in-flight opencontainers/image-tools#8 makes creating layers
easier, although you can find very similar code in containers/storage
(from which opencontainers/image-tools#8 sourced its layer-creation
logic) and docker/docker (from which containers/storage sourced its
layer-creation logic).

@cyphar
Copy link
Member

cyphar commented Oct 19, 2016

I'm not sure if @cyphar is actively maintaining it (he's getting pulled in quite a few directions at the moment ;), but there's also [1].

Yeah, I'm having a busy couple of months 😉. However, I can give some unofficial updates. Currently we at SUSE are planning on integrating some kind of OCI-image-building support into KIWI once image-spec 1.0 is released. I'm going to be heavily involved with that work (which will involve essentially all of the same background work required for oboci). Once the KIWI integration is somewhat working (at least my bits) I'll then work on porting that work over to oboci. My plan was to make oboci the core of the KIWI integration, but we agreed that it's better to keep the two ideas separate (KIWI has a very different methodology when it comes to building images).

@jonboulle
Copy link
Contributor

FWIW, the intention is that acbuild will support OCI images, but this is still a WIP: containers/build#249

@cyphar
Copy link
Member

cyphar commented Oct 19, 2016

The more the merrier. 😉

@TomasTomecek
Copy link
Author

Thanks everyone for all the pointers, this is what I was hoping to get.

@vbatts
Copy link
Member

vbatts commented Mar 9, 2017

cc @erikh has mentioned adding support to box
I think this issue is able to be closed

@jonboulle
Copy link
Contributor

Preliminary support also added in containers/build . I think we can close this out for now and keep ongoing track of implementations via the doc added in #602.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants