Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thierry GUIBERT <thierry.guibert@free.fr>
Cc: Quentin Schulz <quentin.schulz@theobroma-systems.com>,
	Buildroot Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] Docker container for 2022.02.x release
Date: Thu, 25 Aug 2022 20:01:42 +0200	[thread overview]
Message-ID: <20220825180142.GA37358@scaer> (raw)
In-Reply-To: <c9a96eae-198c-7901-515e-74458c3fd8c9@free.fr>

Thierry, All,

On 2022-08-25 19:23 +0200, Thierry GUIBERT spake thusly:
> I think the actual situation is the good one, except that external
> users can't pull images from the gitlab registry

Well, it is certainly possible to pull images from the gitlab.Com
registry:

    $ docker image pull registry.gitlab.com/buildroot.org/buildroot/base:20220206.1756
    20220206.1756: Pulling from buildroot.org/buildroot/base
    955615a668ce: Pull complete
    7d738676681f: Pull complete
    447a312e02d3: Pull complete
    7837e3ad09a2: Pull complete
    efe9d49088e8: Pull complete
    5d2098b1b57e: Pull complete
    Digest: sha256:7d49ba734fbf15e153a8a66c95ae4aeafc7a398353a256f5513e9c6db5e97554
    Status: Downloaded newer image for registry.gitlab.com/buildroot.org/buildroot/base:20220206.1756
    registry.gitlab.com/buildroot.org/buildroot/base:20220206.1756

And as far as I can see, there is even no need to be logged in...

> But knowing that those containers are for development only, I have
> built my own for production firmware construction.

The image used for the Buildroot CI is I belive a very good basis for
building one's own image; that's what I do at $work, where my reference
build environment are docker iamges which Dockerfiles all begin with:
    FROM registry.gitlab.com/buildroot.org/buildroot/base:20220206.1756

> The question could be "what do we do with already published images"
> (especially the one tagged as "latest")

Sicne the gitlab docker registry is publicly available, it would be my
opinion that we drop the iamges on the docker hub. Indeed, docker hub is
rate-limited on the free tier, so unless one has a paid tier, one can't
rely on images hosted in the docker hub.

> It may be described in the documentation, and maybe it already is.

I don't think it is in our manual, except the use of the
utils/docker-run script certainly is hinted about (chapter 17, Adding
support for a particular board).

Extended documentation is most welcome, though! :-)

Regards,
Yann E. MORIN.

> Regards
> 
> On 25/08/2022 18:25, Christian Stewart wrote:
> 
>   I recommend using [1]quay.io instead to avoid the rate limit. 
>   Best,
>   Christian Stewart 
>   On Wed, Aug 24, 2022, 9:20 AM Quentin Schulz < [2]quentin.schulz@theobroma-systems.com> wrote:
> 
>     Hi Yann,
> 
>     On 8/23/22 18:40, Yann E. MORIN wrote:
>     > 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
> 
>     Could Buildroot fit the Docker Open Source Program criteria by any
>     chance? [3]https://www.docker.com/community/open-source/application/
> 
>     That would remove those limitations.
> 
>     If that is not possible or not wanted by the project, I guess that
>     pushing to [4]hub.docker.com but have the Overview page state that this is
>     pull-limited and recommend using the gitlab registry instead?
>     [5]https://hub.docker.com/r/buildroot/base
> 
>     Cheers,
>     Quentin
>     _______________________________________________
>     buildroot mailing list
>     [6]buildroot@buildroot.org
>     [7]https://lists.buildroot.org/mailman/listinfo/buildroot
> 
> Links:
> 1. http://quay.io/
> 2. mailto:quentin.schulz@theobroma-systems.com/
> 3. https://www.docker.com/community/open-source/application/
> 4. http://hub.docker.com/
> 5. https://hub.docker.com/r/buildroot/base
> 6. mailto:buildroot@buildroot.org/
> 7. 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

  reply	other threads:[~2022-08-25 18:01 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
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 [this message]
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=20220825180142.GA37358@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=quentin.schulz@theobroma-systems.com \
    --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