RE: [PATCH v6 0/6] Community Lab Containers and Builder Engine

[Ali Alnubani <alialnu@nvidia.com>]

> -----Original Message-----
> From: Adam Hassick <ahassick@iol.unh.edu>
> Sent: Thursday, May 25, 2023 8:15 PM
> To: ci@dpdk.org
> Cc: aconole@redhat.com; Ali Alnubani <alialnu@nvidia.com>; Adam Hassick
> <ahassick@iol.unh.edu>
> 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/