Re: F24 System Wide Change: Layered Docker Image Build Service

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 03.12.2015 15:40, Adam Miller wrote:
> On Thu, Dec 3, 2015 at 8:12 AM, Tomas Hozza <thozza@xxxxxxxxxx> wrote:
> > On 03.12.2015 14:54, Jan Kurik wrote:
> >> On Thu, Dec 3, 2015 at 2:38 PM, Tomas Hozza <thozza@xxxxxxxxxx> wrote:
> >>> On 03.12.2015 11:40, Jan Kurik wrote:
> >>>> = Proposed System Wide Change: Layered Docker Image Build Service =
> >>>> https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service
> >>>>
> >>>> Change owner(s):
> >>>> * Colin Walters <walters AT redhat DOT com>
> >>>> * Adam Miller <maxamillion AT gmail DOT com >
> >>>> * Tomas Tomecek <ttomecek AT redhat DOT com>
> >>>> * Tim Waugh <twaugh AT redhat DOT com>
> >>>> * Amanda Carter <acarter AT redhat DOT com>
> >>>>
> >>>> Fedora currently ships a Docker base image, but Docker supports a
> >>>> layering concept. There are some applications like Cockpit which we
> >>>> would like to ship as layered applications.
> >>>> This change will deploy the build service to support building and
> >>>> delivering a set of layered Docker images, and will enable Fedora
> >>>> contributors to create and maintain Dockerfiles from which those
> >>>> images will be generated.
> >>>>
> >>>> == Detailed Description ==
> >>>> This change opens up an new type of official binary artifact produced
> >>>> by Fedora. Currently, we produce two main types of artifacts: RPMs,
> >>>> and images. The RPMs are created in Koji from specfiles in dist-git.
> >>>> The images come in different formats, but have in common creation in
> >>>> Koji from kickstart files — this includes the official Fedora Docker
> >>>> Base Image. This change introduces a new type of image, a Docker
> >>>> Layered Image, which is created from a Dockerfile and builds on top of
> >>>> that base image.
> >>>>
> >>>> The system has five major parts:
> >>>>
> >>>> A command-line client — already integrated into rpkg; needs only minor
> >>>> work to enable in fedpkg (there is discussion about either extending
> >>>> fedpkg or adding a new fedcontainer utility)
> >>>> * dist-git for Dockerfiles
> >>>> * A koji plugin, containerbuild
> >>>> * An OpenShift 3 backend
> >>>> * A distribution mechanism; a Docker Registry
> >>>> * Currently evaluating options for this
> >>>> * * Pulp Crane
> >>>> * * Docker Registry
> >>>>
> >>>> == Scope ==
> >>>> For the Scope of this Change please check
> >>>> https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service#Scope
> >>>>
> >>>
> >>> Hi.
> >>>
> >>> The "Ongoing Work Tracking" link does not work.
> >>
> >> Fixed. Thanks for verifying.
> >>
> >>> How is this different from the proposal for Fedora 23 [1]?
> >>> What changed?
> >>
> >> It is not different. The project has started at F23 time however has
> >> not been finished on time. This is continuation of the project.
> >
> > I'm curious to hear from the change owners if anything changed and
> > what pieces that blocked this from being done last time are still pending
> > and what is already done.
>
> It was a few things but the biggest issue was that upstream docker was
> in-flight on retiring the old image format (V1) in favor of the new
> one (V2) which has implications on how a "non-native" docker build
> system (read: something other than the docker daemon) can
> import/export docker images to and from a registry which required a
> lot of re-engineering the backend of the OSBS build system. Basically
> the "docker save" functionality disappeared in V2 upstream without any
> replacement. This work is mostly done and the build system can work
> with V2 registries now.
>
> I'm also not entirely sure this is a "system wide change" as others
> might classify it. For people who are just using Fedora, if we missed
> the deadline or messed something up, they wouldn't notice so it's
> possible this needs to change in classification.

Thank you for the explanation.

Would regular Fedora contributors be able to create and build Layered
Docker images using OSBS? Or will this be usable only for the official
images produced as part of Fedora Products?

E.g. if I think it would be beneficial to ship some package/service that
is already shipped in Fedora as Docker image, will there be any way for
me to leverage OSBS instance in Fedora?

It is not entirely clear to me who is the intended consumer of this - Fedora
releng? Fedora WGs? Regular contributors?

Thanks.

Tomas

> -AdamM
>
> >
> > Thanks.
> >
> > Tomas
> >
> >> Regards,
> >> Jan
> >>
> >>> [1] https://fedorahosted.org/fesco/ticket/1461
> >>>
> >>> Thanks!
> >>>
> >>> Regards,
> >>> --
> >>> Tomas Hozza
> >>> Software Engineer - EMEA ENG Developer Experience
> >>>
> >>> PGP: 1D9F3C2D
> >>> UTC+1 (CET)
> >>> Red Hat Inc.                 http://cz.redhat.com
> >>> --
> >>> devel mailing list
> >>> devel@xxxxxxxxxxxxxxxxxxxxxxx
> >>> http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
> >>
> >>
> >>
> >
> > --
> > Tomas Hozza
> > Software Engineer - EMEA ENG Developer Experience
> >
> > PGP: 1D9F3C2D
> > UTC+1 (CET)
> > Red Hat Inc.                 http://cz.redhat.com
> > --
> > devel mailing list
> > devel@xxxxxxxxxxxxxxxxxxxxxxx
> > http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
> --
> devel mailing list
> devel@xxxxxxxxxxxxxxxxxxxxxxx
> http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
>



-- 
Tomas Hozza
Software Engineer - EMEA ENG Developer Experience

PGP: 1D9F3C2D
UTC+1 (CET)
Red Hat Inc.                 http://cz.redhat.com
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux