From Fedora Project Wiki
m (Nicer formatting)
No edit summary
 
(4 intermediate revisions by one other user not shown)
Line 32: Line 32:
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
-->
-->
* Tracker bug: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1090890 #1090890]


== Detailed Description ==
== Detailed Description ==
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
The [http://index.docker.io public docker registry] hosts many [https://index.docker.io/search?q=fedora fedora images] including an [https://index.docker.io/_/fedora/ unprefixed (semi-official) image]. However, this image doesn't have rel-eng approval which would be required for a fully official image.
The [http://index.docker.io public docker registry] hosts many [https://index.docker.io/search?q=fedora fedora images] including an [https://index.docker.io/_/fedora/ unprefixed (semi-official) image]. However, this image doesn't have rel-eng approval which would be required for a fully official image.
The goal of this change is an unprefixed official image uploaded via Fedora rel-eng to Docker.  Part of the change is to get rel-eng account/access in order to do the upload.


== Benefit to Fedora ==
== Benefit to Fedora ==
Line 44: Line 46:


== Scope ==
== Scope ==
Needs work in Koji to generate Docker base image reliably.  There's conceptually two steps: first the tarball is generated, then it's imported.  This change is still worthwhile even if the image isn't uploaded to the registry, as people could download it directly from Fedora and import it locally.
<!-- What work do the developers have to accomplish to complete the change in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
<!-- What work do the developers have to accomplish to complete the change in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->


Line 118: Line 122:
-->
-->


[[Category:ChangeReadyForWrangler]]
[[Category:ChangeAcceptedF21]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->

Latest revision as of 18:06, 27 June 2014

Docker Container Image

Summary

This is Fedora running inside Docker. Currently, there are non-official images in the docker index, but we'd like them to really come out of release engineering.

Owner

Current status

Detailed Description

The public docker registry hosts many fedora images including an unprefixed (semi-official) image. However, this image doesn't have rel-eng approval which would be required for a fully official image.

The goal of this change is an unprefixed official image uploaded via Fedora rel-eng to Docker. Part of the change is to get rel-eng account/access in order to do the upload.

Benefit to Fedora

This will give docker/fedora users something trustworthy to build other stuff on. Will also give fedora an awesome presence on the docker index :)

Scope

Needs work in Koji to generate Docker base image reliably. There's conceptually two steps: first the tarball is generated, then it's imported. This change is still worthwhile even if the image isn't uploaded to the registry, as people could download it directly from Fedora and import it locally.


  • Proposal owners:

The proposal owner needs to build the image tarballs with the official kickstart scripts and make them available to docker's stackbrew repo, which is used by the Docker maintainers to build unprefixed images.

Release Engineering approval/intervention would be needed at some point (details still TBD)

  • Other developers: N/A (not a System Wide Change)
  • Release engineering: Official Release Engineering image approval. Process still TBD.
  • Policies and guidelines: N/A (not a System Wide Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

N/A (not a System Wide Change)

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

Documentation

Available here.

Release Notes

The Fedora image in the Docker index is now Fully Official! For details, see....