sig_cloud/diskimage-builder
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
a692673b90
diskimage-builder/diskimage_builder/elements/fedora-minimal/README.rst

24 lines
1.0 KiB
ReStructuredText
Raw Normal View History

Add a yum-minimal element that just uses yum The centos-minimal approach of using rinse does not, it turns out, work on centos. That's a bummer. It's also rather heavyweight. Instead, with minor machinations, we can just use yum itself pointed at a chroot. Also adding fedora-minimal element which creates a fedora image using the new yum-minimal approach. Co-Authored-By: Gregory Haynes <greg@greghaynes.net> Change-Id: I026fd9d323e786dae5bb67824c6501067e1ceaa3
2015-03-22 14:04:46 +00:00
==============
fedora-minimal
==============
Update platform support to describe stable testing The reality is that "stable" is what is tested. This tries to give enough info that users can ascertain what tests are running at any given time and hence what elements are known to be working. Additional, clarify the Fedora position in the README as now described by above. Closes: #1653561 Change-Id: Ifb91b9089790897861bd7e671c3dba59adac239d
2017-01-10 04:50:21 +00:00
*Note* as at February 2022, this element is no longer tested or used
by OpenDev. Changes to the RPM format used by recent Fedora releases
have meant that this element can not build on Ubuntu hosts, which lack
a packaged RPM sufficient to extract the base chroot environment. The
``fedora-containerfile`` element can be used instead of this element.
Add a yum-minimal element that just uses yum The centos-minimal approach of using rinse does not, it turns out, work on centos. That's a bummer. It's also rather heavyweight. Instead, with minor machinations, we can just use yum itself pointed at a chroot. Also adding fedora-minimal element which creates a fedora image using the new yum-minimal approach. Co-Authored-By: Gregory Haynes <greg@greghaynes.net> Change-Id: I026fd9d323e786dae5bb67824c6501067e1ceaa3
2015-03-22 14:04:46 +00:00
Create a minimal image based on Fedora.
Use of this element will require 'yum' and 'yum-utils' to be installed on
Ubuntu and Debian. Nothing additional is needed on Fedora or CentOS. The
element will need `python-lzma` everywhere.
Due to a bug in the released version of urlgrabber, on many systems an
installation of urlgrabber from git is required. The git repository
can be found here: http://yum.baseurl.org/gitweb?p=urlgrabber.git;a=summary
Fix DISTRO_NAME in Fedora elements Fix typo in documentation around name variables. Change-Id: I88fd1dd828ce1b606398198dd0317096363480f1
2021-05-17 00:02:09 +00:00
This element sets the ``DISTRO_NAME`` var to 'fedora'. The release of
Remove yum chroot caching Every run we are doing a full tar.gz of the chroot environment that never gets used. It's not suitable for CI since we use fresh images each time there. The cache in general isn't really isn't a very safe thing to have around, because there's no invalidation procedure and no real way to make one -- we've no guarantee that a new chroot build even moments after a previous one wouldn't bring in or different packages, etc (of course this is *unlikely*, but the longer you go between builds the worse the problem becomes. Also, tons of packages get installed after this not from any cache, so potential speed-up is rather marginal. Debian turned this off with I58fc485aacacaa17243bf9ce760ed91256d1f182. However, given the reasons above and it's complete lack of testing, I don't see this as useful. If we really want this type of thing, I think we should come up with a way to use a persistent external yum/dnf cache that yum/dnf keeps in sync with it's usual invalidation rules. Change-Id: I66789c35db75c41bc45ea1ad2e26f87456de4e4d
2016-12-09 03:41:24 +00:00
fedora to be installed can be controlled through the ``DIB_RELEASE``
variable, which defaults the latest supported release.
Reference in New Issue Copy Permalink