From: David Marchand <david.marchand@redhat.com>
To: dev <dev@dpdk.org>
Cc: Aaron Conole <aconole@redhat.com>,
Michael Santana <maicolgabriel@hotmail.com>
Subject: Re: [PATCH v2] ci: add Fedora 35 container in GHA
Date: Sat, 2 Apr 2022 10:01:31 +0200 [thread overview]
Message-ID: <CAJFAV8zH6-te52DUQ1mPsAM_CRMNUsZe0U9zgUia+VpoktBe2A@mail.gmail.com> (raw)
In-Reply-To: <20220401180253.17876-1-david.marchand@redhat.com>
On Fri, Apr 1, 2022 at 8:03 PM David Marchand <david.marchand@redhat.com> wrote:
>
> Build DPDK with Fedora 35 containers.
>
> GHA container support does not allow caching images and docker hub
> seems to limit image pulls.
> On the other hand, the Fedora project hub does not seem to limit them,
> so prefer this hub.
> Nevertheless, let's try to be good citizens and cache (once a day) a
> prepared image for subsequent builds.
We could move to a pipeline approach, with a first stage job preparing
the image and pushing to the cache, and the second stage pulling the
image from the cache and starting compilations.
Food for thoughts...
>
> Differences with the Ubuntu GHA vm images:
> - tasks are run as root in containers, no need for sudo,
> - compiler must be explicitly installed,
> - GHA artifacts can't contain a ':' in their name, and must be filtered,
>
--
David Marchand
next prev parent reply other threads:[~2022-04-02 8:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 12:31 [PATCH] " David Marchand
2021-11-16 14:44 ` Aaron Conole
2021-11-17 17:29 ` David Marchand
2021-11-18 14:17 ` Aaron Conole
2022-04-01 18:02 ` [PATCH v2] " David Marchand
2022-04-02 8:01 ` David Marchand [this message]
2022-04-04 14:24 ` [PATCH v3] " David Marchand
2022-04-04 16:06 ` Aaron Conole
2022-04-06 18:58 ` David Marchand
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=CAJFAV8zH6-te52DUQ1mPsAM_CRMNUsZe0U9zgUia+VpoktBe2A@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=maicolgabriel@hotmail.com \
/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).