28821fd283
We've not really been using the Focal containerfile, as we move forward jammy is a better choice for keeping stable as we might find some new users for it. Also add binutils to bindep for native bullseye builds (see Icb0e40827c9f8ac583fa143545e6bed9641bf613) Change-Id: I22ebe2bbccaec34180e58996b21e47bfc4f36055 |
||
---|---|---|
.. | ||
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.