DPDK CI discussions
 help / color / mirror / Atom feed
From: Adam Hassick <ahassick@iol.unh.edu>
To: Ali Alnubani <alialnu@nvidia.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>,
	"aconole@redhat.com" <aconole@redhat.com>,
	Owen Hilyard <ohilyard@iol.unh.edu>
Subject: Re: [PATCH v6 3/6] containers/builder: Dockerfile creation script
Date: Thu, 22 Jun 2023 12:18:48 -0400	[thread overview]
Message-ID: <CAC-YWqjCoXrSsvR_5K89memiak58qQtkopF-EoXXOMhiUWauTQ@mail.gmail.com> (raw)
In-Reply-To: <DM4PR12MB516730515C681555DCDF7AE1DA22A@DM4PR12MB5167.namprd12.prod.outlook.com>

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

This script is not intended to be run by the end user on their machine's
bare environment. The CI worker container will acquire the needed python
version to run this script when the container is built; the end user does
not need to install python 3.10 themselves. The
"make_docker_files_in_container" target in the Makefile is the intended way
to call this script. The build and push targets then depend on that target.

To me, this appears fine, but let me know if you have any concerns.

On Thu, Jun 22, 2023 at 11:55 AM Ali Alnubani <alialnu@nvidia.com> wrote:

> > -----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>; Owen Hilyard
> > <ohilyard@iol.unh.edu>; Adam Hassick <ahassick@iol.unh.edu>
> > Subject: [PATCH v6 3/6] containers/builder: Dockerfile creation script
> >
> > From: Owen Hilyard <ohilyard@iol.unh.edu>
> >
> > This script will template out all of the Dockerfiles based on the
> > definitions provided in the inventory using the jinja2 templating
> > library.
> >
> [..]
> > +
> > +def get_host_arch() -> str:
> > +    machine: str = platform.machine()
> > +    match machine:
>
> This adds a nondocumented dependency on Python 3.10.
>


-- 
*Adam Hassick*
Senior Developer
UNH InterOperability Lab
ahassick@iol.unh.edu
iol.unh.edu <https://www.iol.unh.edu/>
+1 (603) 475-8248

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

  reply	other threads:[~2023-06-22 16:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-25 17:14 [PATCH v6 0/6] Community Lab Containers and Builder Engine Adam Hassick
2023-05-25 17:15 ` [PATCH v6 1/6] containers/docs: Add container builder start Adam Hassick
2023-05-25 17:15 ` [PATCH v6 2/6] containers/inventory: Add inventory for container builder Adam Hassick
2023-05-25 17:15 ` [PATCH v6 3/6] containers/builder: Dockerfile creation script Adam Hassick
2023-06-22 15:55   ` Ali Alnubani
2023-06-22 16:18     ` Adam Hassick [this message]
2023-06-22 16:52       ` Ali Alnubani
2023-05-25 17:15 ` [PATCH v6 4/6] containers/templates: Templates for Dockerfiles Adam Hassick
2023-06-22 15:40   ` Ali Alnubani
2023-06-22 16:08     ` Adam Hassick
2023-06-22 16:51       ` Ali Alnubani
2023-05-25 17:15 ` [PATCH v6 5/6] containers/container_builder: Container for python scripts Adam Hassick
2023-05-25 17:15 ` [PATCH v6 6/6] containers/Makefile: Makefile to automate builds Adam Hassick
2023-06-22 15:29 ` [PATCH v6 0/6] Community Lab Containers and Builder Engine Ali Alnubani
2023-06-22 19:28   ` Adam Hassick
2023-06-23 14:11     ` Aaron Conole

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=CAC-YWqjCoXrSsvR_5K89memiak58qQtkopF-EoXXOMhiUWauTQ@mail.gmail.com \
    --to=ahassick@iol.unh.edu \
    --cc=aconole@redhat.com \
    --cc=alialnu@nvidia.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).