From Fedora Project Wiki
Line 52: Line 52:
<!-- What work do the feature owners have to accomplish to complete the feature 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 feature owners have to accomplish to complete the feature 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?-->
The proposal owner needs to build the image tarballs with the official kickstart scripts and make them available to docker's [https://github.com/dotcloud/stackbrew stackbrew] repo, which is used by the Docker maintainers to build unprefixed images.
The proposal owner needs to build the image tarballs with the official kickstart scripts and make them available to docker's [https://github.com/dotcloud/stackbrew 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) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->

Revision as of 19:56, 7 April 2014

Important.png
Comments and Explanations
MOSTLY EMPTY TEMPLATE


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

  • Targeted release: Fedora 21
  • Last updated: 2014-04-07
  • Tracker bug: <will be assigned by the Wrangler>

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.

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

  • 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: N/A (not a System Wide Change)
  • 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

N/A (not a System Wide Change)

Release Notes