From Fedora Project Wiki
(Release Notes)
(Scope)
Line 86: Line 86:
 
<!-- What work do other developers 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 other developers 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?-->
  
* Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Release engineering: Will need to add the new container image to the existing scripts that generate Fedora's images. <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.  
 
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.  
 
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.-->
 
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.-->
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: New Minimal Container Image <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->
 
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->
  

Revision as of 15:35, 31 January 2017

Self Contained Change: This change will only affect new users who use the new image.


Container Minimal Image

Summary

Produce a new container image that contains as little as possible, but also still provides the ability to install packages from dnf repositories.

Owner

  • Email: dusty@dustymabe.com
  • Release notes owner:
  • Product: New Minimal Container Image

Current status

  • Targeted release: Fedora 26
  • Last updated: 2017-01-31
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

As a user of Fedora I'd like to build containers based on an image that is a little more lightweight than the current base container image that is produced in Fedora. We have a proof of concept kickstart [1] that will create such an image. It is a work in progress.

[1] https://pagure.io/fedora-kickstarts/pull-request/120


Benefit to Fedora

More options for users who want to build containers based on Fedora.


Scope

  • Proposal owners: Implementation of this Change
  • Other developers: N/A (not a System Wide Change)
  • Release engineering: Will need to add the new container image to the existing scripts that generate Fedora's images.
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

Pull new container image and build other images based on this image and see how it works.

Make sure you can switch from overlay2 back to devicemapper using atomic storage commands. N/A (not a System Wide Change)

User Experience

N/A (not a System Wide Change) Users should not notice the change other then if they use the docker or atomic CLI to examine the storage.

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

Category:ChangeReadyForWrangler