From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thierry GUIBERT <thierry.guibert@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Docker container for 2022.02.x release
Date: Tue, 23 Aug 2022 18:40:40 +0200 [thread overview]
Message-ID: <20220823164040.GH2167049@scaer> (raw)
In-Reply-To: <38884503-637d-7c23-5a02-be8f8c3a522a@free.fr>
Thierry, All,
On 2022-08-23 15:13 +0200, Thierry GUIBERT spake thusly:
> I'm using buildroot to build raspberry pi rootfs for the french red cross.
A noble endeavour, thank you!
> Is there any reason for buildroot/base:20220206.1756 not to be published in
> the docker hub ?
The rationale behind our docker image, is to be able to run our own CI
jobs, that runs in gitlab-CI. Since Docker hub now limits the number of
downloads permonth per image (on fre etier), the CI was very often
blocked from running at all, which was not super nice...
So, we pushed the image to the gitlab registry instead, since the image
raison-d'être was jsut to run in gitlab-CO to begin with.
So, you can get a hint at the actual location of the image, by looking
at out .gitlab-ci.yml file:
image: $CI_REGISTRY/buildroot.org/buildroot/base:20220206.1756
$CI_REGISTRY is a gitlab-CI variable, that points to their registry. Its
value depends on project running the pipeline, and the gitlab-CI hosting
solution. Since we are using gitlab.com, the registry is
registry.gitlab.com. So you should be able to pull:
registry.gitlab.com/buildroot.org/buildroot/base:20220206.1756
> On the hub, the latest container published is 20211120.1925 which does not
> seems to contain python-pytest, so my gitlab pipelines are out of order.
>
> Have you moved to an other docker registry ?
Yep. And since the images are not really meant for direct consumption,
we not longer push them to the dockerhub.
There had been an attempt at providing generic images of various
distributions, taht we wojuld have kinda advertised, but the effort
has stalled...
Regards,
Yann E. MORIN.
> My favorite search engine did not help me this time...
>
> Regards,
>
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-08-23 16:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 13:13 [Buildroot] Docker container for 2022.02.x release Thierry GUIBERT
2022-08-23 16:40 ` Yann E. MORIN [this message]
2022-08-23 19:26 ` Thomas Petazzoni via buildroot
2022-08-24 15:35 ` Yann E. MORIN
2022-08-24 16:20 ` Quentin Schulz
2022-08-25 16:25 ` Christian Stewart via buildroot
2022-08-25 17:23 ` Thierry GUIBERT
2022-08-25 18:01 ` Yann E. MORIN
2022-08-25 21:57 ` Thierry GUIBERT
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=20220823164040.GH2167049@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=thierry.guibert@free.fr \
/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