Announcement: Fedora Docker Layered Image Build Service is GO!

[Adam Miller]

It is with great pleasure that the Fedora Project Announces the availability
of the Fedora Docker Layered Image Build Service[0] to the Fedora Contributor
Community!

With this announcement we are opening availability of the Docker Layered
Image Build Service for the Docker Layered Images[1] that the Fedora Cloud
SIG[2] has been the primary maintainers[3] of on GitHub into DistGit as
official components of Fedora. From there we will be extending an invitation
to all Fedora Contributors to maintain Docker Layered Image Containers for
official release by the Fedora Project. Currently this effort is to enable
the Fedora Cloud/Atomic WG[2] goals which target Fedora Atomic Host[4] as a
primary deliverable to power the future of Cloud. This is also to enable the
Fedora Modularity[5] work be delivered as Containers in the future as Fedora
becomes fundamentally more modular in nature.

How do I get started?

    Contributors will go through a simliar process as what they currently do
with RPM Review Requests. There will be Container Reviews as well as
Container Guidelines:

    https://fedoraproject.org/wiki/Container:Review_Process
    https://fedoraproject.org/wiki/Container:Guidelines

At this time the Cloud/Atomic WG[2] will maintain the Guidelines as well as
the Review Process along with input from all Fedora Contributors. This may
change later with the formation of a Fedora Container Committee (similar to
the Fedora Packaging Committee[6]).

Please note that both the Guidelines and the Review Process are likely to
evolve along with the Container technologies as we move into the future so
we encourage community members to check the documentation for updates.

For more information, please see the following Fedora Community Blog:

   
https://communityblog.fedoraproject.org/fedora-docker-layered-image-build...

[0] - https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service
[1] - https://fedoraproject.org/wiki/Cloud
[2] - https://docs.docker.com/engine/userguide/storagedriver/imagesandcontainers/
[3] - https://github.com/fedora-cloud/Fedora-Dockerfiles
[4] - https://getfedora.org/en/atomic/download/
[5] - https://fedoraproject.org/wiki/Modularity
[6] - https://fedoraproject.org/wiki/Packaging_Committee

[Igor Gnatenko]

On Tue, Dec 13, 2016 at 8:36 PM, Adam Miller
<maxamillion(a)fedoraproject.org&gt; wrote:
>  It is with great pleasure that the Fedora Project Announces the
> availability
>  of the Fedora Docker Layered Image Build Service[0] to the Fedora Contributor
>  Community!
>
>  With this announcement we are opening availability of the Docker Layered
>  Image Build Service for the Docker Layered Images[1] that the Fedora Cloud
>  SIG[2] has been the primary maintainers[3] of on GitHub into DistGit as
>  official components of Fedora. From there we will be extending an invitation
>  to all Fedora Contributors to maintain Docker Layered Image Containers for
>  official release by the Fedora Project. Currently this effort is to enable
>  the Fedora Cloud/Atomic WG[2] goals which target Fedora Atomic Host[4] as a
>  primary deliverable to power the future of Cloud. This is also to enable the
>  Fedora Modularity[5] work be delivered as Containers in the future as Fedora
>  becomes fundamentally more modular in nature.
>
>  How do I get started?
>
>      Contributors will go through a simliar process as what they currently do
>  with RPM Review Requests. There will be Container Reviews as well as
>  Container Guidelines:
>
>      https://fedoraproject.org/wiki/Container:Review_Process
>      https://fedoraproject.org/wiki/Container:Guidelines 
Nice job!

I have couple of questions:
* why "FROM fedora:25", how do I choose version on which I want to
base container?
* is there containers in registry for rawhide?
>  At this time the Cloud/Atomic WG[2] will maintain the Guidelines as well as
>  the Review Process along with input from all Fedora Contributors. This may
>  change later with the formation of a Fedora Container Committee (similar to
>  the Fedora Packaging Committee[6]).
>
>  Please note that both the Guidelines and the Review Process are likely to
>  evolve along with the Container technologies as we move into the future so
>  we encourage community members to check the documentation for updates.
>
>  For more information, please see the following Fedora Community Blog:
>
>     
> https://communityblog.fedoraproject.org/fedora-docker-layered-image-build...
>
>  [0] - https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service
>  [1] - https://fedoraproject.org/wiki/Cloud
>  [2] - https://docs.docker.com/engine/userguide/storagedriver/imagesandcontainers/
>  [3] - https://github.com/fedora-cloud/Fedora-Dockerfiles
>  [4] - https://getfedora.org/en/atomic/download/
>  [5] - https://fedoraproject.org/wiki/Modularity
>  [6] - https://fedoraproject.org/wiki/Packaging_Committee
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org 


-- 
-Igor Gnatenko

[Adam Miller]

On Tue, Dec 13, 2016 at 2:52 PM, Igor Gnatenko <ignatenko(a)redhat.com&gt; wrote:
>  On Tue, Dec 13, 2016 at 8:36 PM, Adam Miller
>  <maxamillion(a)fedoraproject.org&gt; wrote:
> > It is with great pleasure that the Fedora Project Announces the availability
> > of the Fedora Docker Layered Image Build Service[0] to the Fedora Contributor
> > Community!
> >
> > With this announcement we are opening availability of the Docker Layered
> > Image Build Service for the Docker Layered Images[1] that the Fedora Cloud
> > SIG[2] has been the primary maintainers[3] of on GitHub into DistGit as
> > official components of Fedora. From there we will be extending an invitation
> > to all Fedora Contributors to maintain Docker Layered Image Containers for
> > official release by the Fedora Project. Currently this effort is to enable
> > the Fedora Cloud/Atomic WG[2] goals which target Fedora Atomic Host[4] as a
> > primary deliverable to power the future of Cloud. This is also to enable the
> > Fedora Modularity[5] work be delivered as Containers in the future as Fedora
> > becomes fundamentally more modular in nature.
> >
> > How do I get started?
> >
> >     Contributors will go through a simliar process as what they currently do
> > with RPM Review Requests. There will be Container Reviews as well as
> > Container Guidelines:
> >
> >     https://fedoraproject.org/wiki/Container:Review_Process
> >     https://fedoraproject.org/wiki/Container:Guidelines
>  Nice job!
>
>  I have couple of questions:
>  * why "FROM fedora:25", how do I choose version on which I want to
>  base container? 
The 'FROM fedora:25' line should coordinate with the branch of DistGit
you're working in. Since Docker doesn't have a mechanism like RPMs do
with macros where we can parameterize things like that, we just have
to define it for now (we may later change it to where the 'FROM
fedora:$version' is inferred and something makes a modification to the
Dockerfile before building.

>  * is there containers in registry for rawhide? 
There are not at this moment, only for Fedora 24 and Fedora 25. I hope
to have rawhide enabled very soon though. The layout of DistGit
branches correlated to Fedora release information fed into the Build
System is something that needs be sorted since "branched" Fedora
Releases have a version number tied to DistGit but Rawhide is
technically f26 right now. I'll update as soon as this is live.

-AdamM

>>
>> At this time the Cloud/Atomic WG[2] will maintain the Guidelines as well as
>> the Review Process along with input from all Fedora Contributors. This may
>> change later with the formation of a Fedora Container Committee (similar to
>> the Fedora Packaging Committee[6]).
>>
>> Please note that both the Guidelines and the Review Process are likely to
>> evolve along with the Container technologies as we move into the future so
>> we encourage community members to check the documentation for updates.
>>
>> For more information, please see the following Fedora Community Blog:
>>
>>    
https://communityblog.fedoraproject.org/fedora-docker-layered-image-build...
>>
>> [0] - https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service
>> [1] - https://fedoraproject.org/wiki/Cloud
>> [2] -
https://docs.docker.com/engine/userguide/storagedriver/imagesandcontainers/
>> [3] - https://github.com/fedora-cloud/Fedora-Dockerfiles
>> [4] - https://getfedora.org/en/atomic/download/
>> [5] - https://fedoraproject.org/wiki/Modularity
>> [6] - https://fedoraproject.org/wiki/Packaging_Committee
>> _______________________________________________
>> devel mailing list -- devel(a)lists.fedoraproject.org
>> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>
>
>
> --
> -Igor Gnatenko
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org

[Adam Miller]

On Tue, Dec 13, 2016 at 4:18 PM, Adam Miller
<maxamillion(a)fedoraproject.org&gt; wrote:
>  On Tue, Dec 13, 2016 at 2:52 PM, Igor Gnatenko
> <ignatenko(a)redhat.com&gt; wrote:
> > On Tue, Dec 13, 2016 at 8:36 PM, Adam Miller
> > <maxamillion(a)fedoraproject.org&gt; wrote:
> >> It is with great pleasure that the Fedora Project Announces the availability
> >> of the Fedora Docker Layered Image Build Service[0] to the Fedora Contributor
> >> Community!
> >>
> >> With this announcement we are opening availability of the Docker Layered
> >> Image Build Service for the Docker Layered Images[1] that the Fedora Cloud
> >> SIG[2] has been the primary maintainers[3] of on GitHub into DistGit as
> >> official components of Fedora. From there we will be extending an invitation
> >> to all Fedora Contributors to maintain Docker Layered Image Containers for
> >> official release by the Fedora Project. Currently this effort is to enable
> >> the Fedora Cloud/Atomic WG[2] goals which target Fedora Atomic Host[4] as a
> >> primary deliverable to power the future of Cloud. This is also to enable the
> >> Fedora Modularity[5] work be delivered as Containers in the future as Fedora
> >> becomes fundamentally more modular in nature.
> >>
> >> How do I get started?
> >>
> >>     Contributors will go through a simliar process as what they currently do
> >> with RPM Review Requests. There will be Container Reviews as well as
> >> Container Guidelines:
> >>
> >>     https://fedoraproject.org/wiki/Container:Review_Process
> >>     https://fedoraproject.org/wiki/Container:Guidelines
> > Nice job!
> >
> > I have couple of questions:
> > * why "FROM fedora:25", how do I choose version on which I want to
> > base container?
>
>  The 'FROM fedora:25' line should coordinate with the branch of DistGit
>  you're working in. Since Docker doesn't have a mechanism like RPMs do
>  with macros where we can parameterize things like that, we just have
>  to define it for now (we may later change it to where the 'FROM
>  fedora:$version' is inferred and something makes a modification to the
>  Dockerfile before building.
>
> > * is there containers in registry for rawhide?
>
>  There are not at this moment, only for Fedora 24 and Fedora 25. I hope
>  to have rawhide enabled very soon though. The layout of DistGit
>  branches correlated to Fedora release information fed into the Build
>  System is something that needs be sorted since "branched" Fedora
>  Releases have a version number tied to DistGit but Rawhide is
>  technically f26 right now. I'll update as soon as this is live. 
Rawhide is now live, you can 'fedpkg container-build' from DistGit
master branch just like you can 'fedpkg build' for rawhide RPMs.

Apologies for the delay,
-AdamM

>
> -AdamM
>
>>>
>>> At this time the Cloud/Atomic WG[2] will maintain the Guidelines as well as
>>> the Review Process along with input from all Fedora Contributors. This may
>>> change later with the formation of a Fedora Container Committee (similar to
>>> the Fedora Packaging Committee[6]).
>>>
>>> Please note that both the Guidelines and the Review Process are likely to
>>> evolve along with the Container technologies as we move into the future so
>>> we encourage community members to check the documentation for updates.
>>>
>>> For more information, please see the following Fedora Community Blog:
>>>
>>>    
https://communityblog.fedoraproject.org/fedora-docker-layered-image-build...
>>>
>>> [0] -
https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service
>>> [1] - https://fedoraproject.org/wiki/Cloud
>>> [2] -
https://docs.docker.com/engine/userguide/storagedriver/imagesandcontainers/
>>> [3] - https://github.com/fedora-cloud/Fedora-Dockerfiles
>>> [4] - https://getfedora.org/en/atomic/download/
>>> [5] - https://fedoraproject.org/wiki/Modularity
>>> [6] - https://fedoraproject.org/wiki/Packaging_Committee
>>> _______________________________________________
>>> devel mailing list -- devel(a)lists.fedoraproject.org
>>> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>>
>>
>>
>> --
>> -Igor Gnatenko
>> _______________________________________________
>> devel mailing list -- devel(a)lists.fedoraproject.org
>> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org

[Trishna Guha]

On Wed, Dec 14, 2016 at 1:06 AM, Adam Miller
<maxamillion(a)fedoraproject.org&gt; wrote:
>      Contributors will go through a simliar process as what they
> currently do
>  with RPM Review Requests. There will be Container Reviews as well as
>  Container Guidelines: 
Absolutely great news.

I have couple of questions regarding Container review process.
After container build are we going to request updates for fedora
release braches using Bodhi?
As discussed in 15-12-2016 Atomic-wg meeting we are going to have
taskotron automated testcases as well.
Are these all going to use Bodhi interface like it happens for RPM packages?


-- 
Regards,
Trishna Guha

trishnaguha17(a)gmail.com
trishnag.wordpress.com

[Adam Miller]

On Thu, Dec 15, 2016 at 5:49 AM, Trishna Guha <trishnaguha17(a)gmail.com&gt; wrote:
>  On Wed, Dec 14, 2016 at 1:06 AM, Adam Miller
>  <maxamillion(a)fedoraproject.org&gt; wrote:
> >     Contributors will go through a simliar process as what they currently do
> > with RPM Review Requests. There will be Container Reviews as well as
> > Container Guidelines:
>
>  Absolutely great news.
>
>  I have couple of questions regarding Container review process.
>  After container build are we going to request updates for fedora
>  release braches using Bodhi?
>  As discussed in 15-12-2016 Atomic-wg meeting we are going to have
>  taskotron automated testcases as well.
>  Are these all going to use Bodhi interface like it happens for RPM packages?
>  
At this time there will not be Bodhi updates, but there will be a
RelEng process that will perform releases every other week
(alternating with the weeks that we do Two Week Atomic Releases). Once
the Taskotron work is in place (being released soon), we'll have
automated testing happening on every container build in koji and then
there will be fedmsg data stored in datagrepper that we can query to
find out the latest version of a container that is successfully
passing all it's tests.

I'll update the wiki page with information about this.

-AdamM

>
> --
> Regards,
> Trishna Guha
>
> trishnaguha17(a)gmail.com
> trishnag.wordpress.com
> _______________________________________________
> cloud mailing list -- cloud(a)lists.fedoraproject.org
> To unsubscribe send an email to cloud-leave(a)lists.fedoraproject.org