6802cf7100
The dib-run-parts element was copying our internal version of dib-run-parts into /usr/local/bin to be used running scripts inside the target chroot. However, it never cleaned up after itself. This means all images were left with an unmanaged local install of dib-run-parts. This copies dib-run-parts into the hooks directory of the chroot and runs it from there. It is cleaned up automatically on the exit path. The dib-run-parts element is no longer required and it has been removed from all dependencies. It is left with a deprecation notice in the README. For compatability we convert it to simply install dib-utils. Codesearch shows no users depending on this unintentional implicit install. Note os-refresh-config depends on dib-utils and thus will have an explicitly installed version. Partial-Bug: #1673144 Change-Id: Ia2e96c00a4246c04beb96c17f83b8aefb69219ca |
||
|---|---|---|
| .. | ||
| extra-data.d | ||
| root.d | ||
| element-provides | ||
| README.rst | ||
====== docker ====== Base element for creating images from docker containers. This element is incomplete by itself, you'll want to add additional elements, such as dpkg or yum to get richer features. At its heart, this element simply exports a root tarball from a named docker container so that other diskimage-builder elements can build on top of it. The variables `DISTRO_NAME` and `DIB_RELEASE` will be used to decide which docker image to pull, and are required for most other elements. Additionally, the `DIB_DOCKER_IMAGE` environment variable can be set in addition to `DISTRO_NAME` and `DIB_RELEASE` if a different docker image is desired.