From: Anthony Green <green@moxielogic.com>
To: libffi-discuss <libffi-discuss@sourceware.org>
Subject: Re: Dockerhub rate limiting impacting libffi testing -- solutions?
Date: Thu, 25 Mar 2021 09:25:55 -0400 [thread overview]
Message-ID: <CACxje5-f58eZQD4grSxZTSMwpahyfB3R=Zg=z-gocHQAzEkE+Q@mail.gmail.com> (raw)
In-Reply-To: <CACxje5-ByC=kfVzFNSc9jxB+x41K7c86WT=K3Y3b2ZpO+kVagA@mail.gmail.com>
The answer was delivered quickly... simply rehost those images on quay.io
(some of the emulators were already hosted there). Apologies for the
noise -- but it helped me get my answer!
AG
On Thu, Mar 25, 2021 at 8:56 AM Anthony Green <green@moxielogic.com> wrote:
> libffi CI testing relies heavily on OCI-compatible images containing cross
> toolchains and emulators. Those container images are hosted in
> dockerhub and pulled down for use on travis-ci. It only takes a few PRs
> or commits for us to exceed our free dockerhub daily quota. I don't have
> a lot of time to look into this, so I'm hoping somebody out there has an
> informed opinion on where we can rehost those images for free, or solve the
> rate-limiting problem with dockerhub.
>
> I want to solve this quickly in order to get a new release out before too
> long.
>
> Thank you for your ideas!
>
> AG
>
>
prev parent reply other threads:[~2021-03-25 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 12:56 Anthony Green
2021-03-25 13:25 ` Anthony Green [this message]
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='CACxje5-f58eZQD4grSxZTSMwpahyfB3R=Zg=z-gocHQAzEkE+Q@mail.gmail.com' \
--to=green@moxielogic.com \
--cc=libffi-discuss@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).