From Fedora Project Wiki

< Changes

Revision as of 21:57, 24 April 2017 by Walters (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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

Container Minimal Image


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

Builds for Fedora 26 Alpha can be found here:

Koji builds:


curl | docker load
docker run --rm -ti fedora-container-minimal-base-26_alpha-1.7.x86_64 bash
microdnf install httpd

Currently, builds of this are not automatically pushed to any registry. The plan however is for this to be regularly updated once Fedora 26 final is released.


  • Email:
  • Release notes owner:
  • Product: New Minimal Container Image

Current status

You can find builds here:

Note that the build is currently flaky:

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.


Benefit to Fedora

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


  • 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.


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


N/A (not a System Wide Change)

Release Notes