These changes are based off of an internal copy that should've been kept up-to-date with the latest patch series. This internal copy is what we're running in production to build our images. This is where I made my changes when adding documentation for new features. I'll make sure that the changes Owen was asked to add between the initial patchset and the v4 patchset are present in what we have running in production and in the next patch. On an unrelated note, the version of the arch dockerfile template in this patch no longer builds without error. This is due to a change in the arch base image that prevents the installation of pip packages in the root environment. I will include those changes in the next patchset as well. On Thu, Jun 22, 2023 at 11:29 AM Ali Alnubani wrote: > > -----Original Message----- > > From: Adam Hassick > > Sent: Thursday, May 25, 2023 8:15 PM > > To: ci@dpdk.org > > Cc: aconole@redhat.com; Ali Alnubani ; Adam Hassick > > > > Subject: [PATCH v6 0/6] Community Lab Containers and Builder Engine > > > > This patch series contains a new version of the DPDK CI containers. The > old > > version was tied very tightly to the Community Lab Infrastructure, so it > was > > not suitable for general use. This version is designed to make adding new > > OSes or OS versions as easy as possible. The minimum functionality can > easily > > be built on any system that can compile DPDK. It includes support for > > building containers for other non-native architectures (ex: arm > containers > > on x86) and for baking ABI references into the images. Support for > > building the Coverity Scan container image has also been added. > > > > The inventory file as added in this patch series defines what the > community > > lab > > currently supports. > > > > If you want to build these yourself, don't try to do parallel Makefile > builds > > on non-server hardware. Libabigail is built into the containers, and > since it > > is not avaliable in all distros it is compiled from source for many > targets. > > If embedding the abi is enabled (DPDK_CI_CONTAINERS_BUILD_ABI=Y), with > > the > > current settings, DPDK will be compiled thrice for every target in the > > inventory file. Due to how the containers are constructed, building on > > non-native architectures is especially expensive because DPDK is > compiled with > > an emulated compiler in a qemu vm that only has one thread. > > > > Hi Adam, > > Are you sure your changes were based on Owen's most recent patchset (v4)? > I noticed that the README no longer mentions the dependency on podman > v4.0.0. See: > https://inbox.dpdk.org/ci/DM4PR12MB51677D9D8DBCD1A3D7D3997DDA2B9@DM4PR12MB5167.namprd12.prod.outlook.com/ > -- *Adam Hassick* Senior Developer UNH InterOperability Lab ahassick@iol.unh.edu iol.unh.edu +1 (603) 475-8248