From: Ali Alnubani <alialnu@nvidia.com>
To: "ohilyard@iol.unh.edu" <ohilyard@iol.unh.edu>,
"ci@dpdk.org" <ci@dpdk.org>
Cc: "aconole@redhat.com" <aconole@redhat.com>
Subject: RE: [PATCH 5/6] containers/container_builder: Container for python scripts
Date: Tue, 11 Oct 2022 20:24:56 +0000 [thread overview]
Message-ID: <DM4PR12MB51670DF579631BDCF43FA006DA239@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20221011165255.506428-6-ohilyard@iol.unh.edu>
> -----Original Message-----
> From: ohilyard@iol.unh.edu <ohilyard@iol.unh.edu>
> Sent: Tuesday, October 11, 2022 7:53 PM
> To: ci@dpdk.org
> Cc: aconole@redhat.com; Owen Hilyard <ohilyard@iol.unh.edu>
> Subject: [PATCH 5/6] containers/container_builder: Container for python
> scripts
>
> From: Owen Hilyard <ohilyard@iol.unh.edu>
>
> Adds a container that can be used to run the python scripts to create
> the Dockerfiles for the CI containers. This removes a large number of
> python environment dependencies from the host requirements.
>
> Signed-off-by: Owen Hilyard <ohilyard@iol.unh.edu>
> ---
[..]
> +COPY template_engine/pyproject.toml /tmp/pyproject.toml
> +COPY template_engine/poetry.lock /tmp/poetry.lock
A clean repo won't have poetry.lock, which would cause this step to fail.
[..]
next prev parent reply other threads:[~2022-10-11 20:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 16:52 [PATCH 0/6] Community Lab Container Definitions ohilyard
2022-10-11 16:52 ` [PATCH 1/6] containers/docs: Add container builder start ohilyard
2022-10-11 16:52 ` [PATCH 2/6] containers/inventory: Add inventory for container builder ohilyard
2022-10-11 20:24 ` Ali Alnubani
2022-10-11 16:52 ` [PATCH 3/6] containers/builder: Dockerfile creation script ohilyard
2022-10-11 16:52 ` [PATCH 4/6] containers/templates: Templates for Dockerfiles ohilyard
2022-10-11 20:24 ` Ali Alnubani
2022-10-11 16:52 ` [PATCH 5/6] containers/container_builder: Container for python scripts ohilyard
2022-10-11 20:24 ` Ali Alnubani [this message]
2022-10-11 16:52 ` [PATCH 6/6] containers/Makefile: Makefile to automate builds ohilyard
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=DM4PR12MB51670DF579631BDCF43FA006DA239@DM4PR12MB5167.namprd12.prod.outlook.com \
--to=alialnu@nvidia.com \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=ohilyard@iol.unh.edu \
/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).