DPDK CI discussions
 help / color / mirror / Atom feed
From: Owen Hilyard <ohilyard@iol.unh.edu>
To: Ali Alnubani <alialnu@nvidia.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>, "aconole@redhat.com" <aconole@redhat.com>
Subject: Re: [PATCH v2 4/6] containers/templates: Templates for Dockerfiles
Date: Mon, 24 Oct 2022 08:52:04 -0400	[thread overview]
Message-ID: <CAHx6DYAxKaOxSw+=-gdUjTQtYwjeYZH8=Xaa=2jfpeK=5Aqq2Q@mail.gmail.com> (raw)
In-Reply-To: <DM4PR12MB5167D68112686F167EFCED43DA2B9@DM4PR12MB5167.namprd12.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2267 bytes --]

On Wed, Oct 19, 2022 at 3:24 PM Ali Alnubani <alialnu@nvidia.com> wrote:

> > -----Original Message-----
> > From: ohilyard@iol.unh.edu <ohilyard@iol.unh.edu>
> > Sent: Wednesday, October 19, 2022 3:53 PM
> > To: ci@dpdk.org
> > Cc: aconole@redhat.com; Ali Alnubani <alialnu@nvidia.com>; Owen Hilyard
> > <ohilyard@iol.unh.edu>
> > Subject: [PATCH v2 4/6] containers/templates: Templates for Dockerfiles
> >
> > From: Owen Hilyard <ohilyard@iol.unh.edu>
> >
> > Adds a variety of extensible templates used to create the Dockerfiles
> > for each target. All templates inherit from base, and most distros and
> > distro families have their own templates that are used to define common
> > functionality. Multiple versions of a distro may use a single template
> > if they are similar enough (ex: fedora).
> >
> > Signed-off-by: Owen Hilyard <ohilyard@iol.unh.edu>
> > ---
> [..]
> > diff --git
> > a/containers/template_engine/templates/containers/base.dockerfile.j2
> > b/containers/template_engine/templates/containers/base.dockerfile.j2
> > new file mode 100644
> > index 0000000..c6194e9
> > --- /dev/null
> > +++ b/containers/template_engine/templates/containers/base.dockerfile.j2
> > @@ -0,0 +1,81 @@
> [..]
> > +# install libabigail
> > +{% block install_libabigail %}
> > +COPY libabigail libabigail
> > +RUN --mount=type=cache,target=/ccache cd libabigail && mkdir build &&
> > autoreconf -i && cd build && ../configure --prefix=/usr/local && make all
> > install && \
> > +    ldconfig && cd .. && rm -rf libabigail
>
> Current directory is /libabigail/build/. You need to go back another
> directory before executing "rm -rf libabigail".
>
> $ podman run -it --rm localhost/ubuntu20.04_compile
> $ du -chs /libabigail/
> 1.9G    /libabigail/
> 1.9G    total
>

I'll fix that for v3.


> By the way, do we have to build libabigail when
> DPDK_CI_CONTAINERS_BUILD_ABI is disabled?
>

Technically no, but libabigail is installed via the package manager for
distros that have it (Fedora, RHEL 7 & 8, and a few others). At UNH, we
value environment consistency (same tools in every container) much more
than disk space or build time. I'll add an option for anyone who has
different preferences/priorities in v3.


> > +{% endblock install_libabigail %}
> [..]
>

[-- Attachment #2: Type: text/html, Size: 3686 bytes --]

  reply	other threads:[~2022-10-24 12:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 12:53 [PATCH v2 0/6] Community Lab Container Definitions ohilyard
2022-10-19 12:53 ` [PATCH v2 1/6] containers/docs: Add container builder start ohilyard
2022-10-19 12:53 ` [PATCH v2 2/6] containers/inventory: Add inventory for container builder ohilyard
2022-10-19 12:53 ` [PATCH v2 3/6] containers/builder: Dockerfile creation script ohilyard
2022-10-19 12:53 ` [PATCH v2 4/6] containers/templates: Templates for Dockerfiles ohilyard
2022-10-19 19:24   ` Ali Alnubani
2022-10-24 12:52     ` Owen Hilyard [this message]
2022-10-19 12:53 ` [PATCH v2 5/6] containers/container_builder: Container for python scripts ohilyard
2022-10-19 12:53 ` [PATCH v2 6/6] containers/Makefile: Makefile to automate builds ohilyard
2022-10-19 14:31 ` [PATCH v2 0/6] Community Lab Container Definitions Ali Alnubani
2022-10-19 14:55   ` Owen Hilyard
2022-10-20  8:25 ` Ali Alnubani

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHx6DYAxKaOxSw+=-gdUjTQtYwjeYZH8=Xaa=2jfpeK=5Aqq2Q@mail.gmail.com' \
    --to=ohilyard@iol.unh.edu \
    --cc=aconole@redhat.com \
    --cc=alialnu@nvidia.com \
    --cc=ci@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).