ce410de834
Because we are using the building platform's "yum" to do the initial install into the chroot, it is affected by the base-system's /etc/yum.conf. pip-and-virtaulenv in I82acb865378a0fa5903a6267bfcee0e2962eced0 added "exclude=python-pip..." in /etc/yum.conf to stop the package manager overwriting the installed pip. Now our CI images have built with this, we are now picking up this exclude on centos. Since on F24 dnf->python->python-pip we end up failing to build the the chroot because python-pip can not be satisifed. In a general sense, however, this could be caused by any configuration put into /etc/yum.conf that is incompatible with installing into the chroot. yum has the option to disable all excludes which is used here. This seems to be the best way to isolate the chroot install from any excludes that may have been done on the base system for various reasons. I did consider using a completely separate yum.conf we ship with dib ... but let's start simple. This should fix the current gate failures on centos Change-Id: I4e4cc8ed09a29c4057ade34ea93025139e191bf5 |
||
|---|---|---|
| .. | ||
| install.d | ||
| pre-install.d | ||
| root.d | ||
| element-deps | ||
| package-installs.yaml | ||
| pkg-map | ||
| README.rst | ||
=========== yum-minimal =========== Base element for creating minimal yum-based images. This element is incomplete by itself, you'll want to use the centos-minimal or fedora-minimal elements to get an actual base image. 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 `DIB_OFFLINE` or more specific `DIB_YUMCHROOT_USE_CACHE` variables can be set to prefer the use of a pre-cached root filesystem tarball. If you wish to have DHCP networking setup for eth0 & eth1 via /etc/sysconfig/network-config scripts/ifcfg-eth[0|1], set the environment variable `DIB_YUM_MINIMAL_CREATE_INTERFACES` to `1`.