41aa936fa2
These must have broken when we switched the base nodes to Jammy. Update to use compatible versions of distros. We need to squish another gate-breaking change in here to update the containerfile "podman build" calls to use "--network host". We added this with Ia885237406bf4c7b9d49b349f374558ae746401f and the only external user I can find is kayobe, which is setting this anyway. I honestly haven't 100% root-caused what changed to require this; the last time our containerfile jobs ran and worked has unfortunately been purged so I can't compare versions to try and pinpoint something; i.e. this may be a podman bug or feature. At first I thought it related to the networking plugin package from the Depends-On (which is still useful for the right packages) but that didn't help get the bridge networking working. Depends-On: https://review.opendev.org/c/zuul/nodepool/+/867590 Change-Id: I23f091654cb212e8bdd908664b262de9bfe98cef |
||
|---|---|---|
| .. | ||
| root.d | ||
| test-elements/jammy-build-succeeds | ||
| element-provides | ||
| README.rst | ||
=============
containerfile
=============
Base element for creating images from container files (aka
Dockerfiles).
Usually this element will be called via a more specific distro element
which provides an environment for building a full image. This element
will search active elements for a container file located in
``containerfiles/${DIB_RELEASE}``.
Alternatively, to use this element directly supply the path to a
container file in the environment variable
``DIB_CONTAINERFILE_DOCKERFILE``.
Set ``DIB_CONTAINERFILE_RUNTIME`` to ``docker`` to use Docker for building
images (default is ``podman``).
Set ``DIB_CONTAINERFILE_RUNTIME_ROOT`` to ``1`` to run the runtime
(Docker or ``podman``, per above) as ``root``.
Set ``DIB_CONTAINERFILE_NETWORK_DRIVER`` to a network driver of your choice
(e.g. host) to use it instead of the default bridge during build.