Re: F26 Self Contained Change: Container Minimal Image
On Wed, Feb 1, 2017 at 12:21 PM Matthew Miller > It is the DNF team. I have a hope that these will be fronted by a > command called "yum" which will implement close-to-full compatibility > with Yum Classic > Would be nice to have this available in general Fedora releases by default as well. The yum -> dnf transition still feels like needless churn as a end user tool but having a yum command just do the right thing as always will help Rahul ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: F26 Self Contained Change: Container Minimal Image
On Wed, 2017-02-01 at 11:12 -0500, Dusty Mabe wrote: > > On 01/31/2017 09:54 AM, Zbigniew Jędrzejewski-Szmek wrote: > > On Tue, Jan 31, 2017 at 09:00:01AM +0100, Jan Kurik wrote: > > > = Proposed Self Contained Change: Container Minimal Image = > > > https://fedoraproject.org/wiki/Changes/ContainerMinimalImage > > > > > > Change owner(s): > > > * Dusty Mabe > > > > > > > > > Produce a new container image that contains as little as possible, but > > > also still provides the ability to install packages from dnf > > > repositories. > > > > Would this be an official image or just a "contrib" kickstart? > > If the first, shouldn't it be added to the list of deliverables, and > > who's going to test it, etc. > > > > > I would hope that this would be an official image. I imagine testing > would be a joint effort between the atomic WG and the QA team. This > is my first go-round on this front so I welcome guidance on the appropriate > process to take. Zbigniew is pretty much on point: it would at least need to be added to the official list of deliverables: https://fedoraproject.org/wiki/Releases/26/ReleaseBlocking (or an existing entry updated if it's replacing an existing image), and a decision made on whether it's 'release blocking'. If it's going to be part of two-week Atomic I guess you'll want to work with Kushal and Sayan for now to make sure it's tested in Autocloud/Tunir. If you want any manual testing done on it we'd need to figure that out; we have https://fedoraproject.org/wiki/Template:Cloud_test_matrix for testing Cloud images as part of the traditional 'release validation' process, but we really don't have anything for doing manual testing as part of the two-week Atomic process, which is probably an oversight we should correct... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: F26 Self Contained Change: Container Minimal Image
On Wed, Feb 01, 2017 at 04:14:21PM +, Peter Robinson wrote: > Who supports microdnf? Is that the dnf team or others? It is the DNF team. I have a hope that these will be fronted by a command called "yum" which will implement close-to-full compatibility with Yum Classic, and which will: 1. Use full dnf backend if available 2. Fall back to microdnf otherwise 3. And if microdnf can't handle it, tell me so, install full dnf backend, and continue. -- Matthew MillerFedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: F26 Self Contained Change: Container Minimal Image
>>> = Proposed Self Contained Change: Container Minimal Image = >>> https://fedoraproject.org/wiki/Changes/ContainerMinimalImage >>> >>> Change owner(s): >>> * Dusty Mabe >>> >>> >>> Produce a new container image that contains as little as possible, but >>> also still provides the ability to install packages from dnf >>> repositories. >> >> How's this different to the minimal container we currently ship? > > The goal is to get it smaller that what we currently ship. Part of > this is being done by removing dnf (and thus python) from the image > by using microdnf instead. The goal really is to rip out most anything > that doesn't make sense and/or is bloated for a container use case. Who supports microdnf? Is that the dnf team or others? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: F26 Self Contained Change: Container Minimal Image
On 01/31/2017 09:54 AM, Zbigniew Jędrzejewski-Szmek wrote: > On Tue, Jan 31, 2017 at 09:00:01AM +0100, Jan Kurik wrote: >> = Proposed Self Contained Change: Container Minimal Image = >> https://fedoraproject.org/wiki/Changes/ContainerMinimalImage >> >> Change owner(s): >> * Dusty Mabe >> >> >> Produce a new container image that contains as little as possible, but >> also still provides the ability to install packages from dnf >> repositories. > > Would this be an official image or just a "contrib" kickstart? > If the first, shouldn't it be added to the list of deliverables, and > who's going to test it, etc. > I would hope that this would be an official image. I imagine testing would be a joint effort between the atomic WG and the QA team. This is my first go-round on this front so I welcome guidance on the appropriate process to take. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: F26 Self Contained Change: Container Minimal Image
On 01/31/2017 10:35 AM, Peter Robinson wrote: > On Tue, Jan 31, 2017 at 8:00 AM, Jan Kurikwrote: >> = Proposed Self Contained Change: Container Minimal Image = >> https://fedoraproject.org/wiki/Changes/ContainerMinimalImage >> >> Change owner(s): >> * Dusty Mabe >> >> >> Produce a new container image that contains as little as possible, but >> also still provides the ability to install packages from dnf >> repositories. > > How's this different to the minimal container we currently ship? The goal is to get it smaller that what we currently ship. Part of this is being done by removing dnf (and thus python) from the image by using microdnf instead. The goal really is to rip out most anything that doesn't make sense and/or is bloated for a container use case. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: F26 Self Contained Change: Container Minimal Image
On Tue, Jan 31, 2017 at 8:00 AM, Jan Kurikwrote: > = Proposed Self Contained Change: Container Minimal Image = > https://fedoraproject.org/wiki/Changes/ContainerMinimalImage > > Change owner(s): > * Dusty Mabe > > > Produce a new container image that contains as little as possible, but > also still provides the ability to install packages from dnf > repositories. How's this different to the minimal container we currently ship? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: F26 Self Contained Change: Container Minimal Image
On Tue, Jan 31, 2017 at 09:00:01AM +0100, Jan Kurik wrote: > = Proposed Self Contained Change: Container Minimal Image = > https://fedoraproject.org/wiki/Changes/ContainerMinimalImage > > Change owner(s): > * Dusty Mabe > > > Produce a new container image that contains as little as possible, but > also still provides the ability to install packages from dnf > repositories. Would this be an official image or just a "contrib" kickstart? If the first, shouldn't it be added to the list of deliverables, and who's going to test it, etc. Zbyszek > == 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 > > > == Scope == > * Proposal owners: > Implementation of this Change > > * Other developers: > N/A (not a System Wide Change) > > * Release engineering: > N/A (not a System Wide Change) > > * List of deliverables: > N/A (not a System Wide Change) > > * Policies and guidelines: > N/A (not a System Wide Change) > > * Trademark approval: > N/A (not needed for this Change) > -- > Jan Kuřík > Platform & Fedora Program Manager > Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org