[Buildroot] Docker container for 2022.02.x release

[Buildroot] Docker container for 2022.02.x release

[Thierry GUIBERT]

Hi folks,

I'm using buildroot to build raspberry pi rootfs for the french red cross.

Is there any reason for buildroot/base:20220206.1756 not to be published 
in the docker hub ?

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 ?

My favorite search engine did not help me this time...

Regards,


_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] Docker container for 2022.02.x release

[Yann E. MORIN]

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

Re: [Buildroot] Docker container for 2022.02.x release

[Thomas Petazzoni via buildroot]

Hello,

On Tue, 23 Aug 2022 18:40:40 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> > 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...

I really think we should change the buildroot/base image to be a
"basic" image with really the minimal requirements for Buildroot, and
publish this image on DockerHub. Then, we should have a buildroot/ci
image that is in the Gitlab registry, and used by our Gitlab CI jobs.

Anyone willing to work on this? :-)

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] Docker container for 2022.02.x release

[Yann E. MORIN]

Thomas, All,

On 2022-08-23 21:26 +0200, Thomas Petazzoni spake thusly:
> On Tue, 23 Aug 2022 18:40:40 +0200
> "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> 
> > > 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...
> 
> I really think we should change the buildroot/base image to be a
> "basic" image with really the minimal requirements for Buildroot, and
> publish this image on DockerHub. Then, we should have a buildroot/ci
> image that is in the Gitlab registry, and used by our Gitlab CI jobs.

But I think the current situation is already easy enough.

 1. people who want to try Buildroot can already use the current image:
    they just have to pull from the gitlb registry instead of the docker
    hub; there is even the utils/docker-run helper script that can be
    used to either  enter an interactive shell, or spawn an arbitrary
    command;

 2. people who want to generate their own image with more than the base
    minimum: they can point their Dockerfile FROM to our image in the
    gitlab registry;

 3. people who want to test build failures: again, pulling the image
    from the gitlab registry is easy enough, and this is not even
    required as the helper script will wrap all that.

The only caveat here, is that we should maybe better advertise that the
official image is in the gitlab registry, not the dockerhub.

So, I thik that our image should still be a base image that is only
suited for our CI, and if we need something else, then we should build
on top of that.

Finally, there is a fourth usage, that I know Thomas already complained
about, is that it is not possible to become root in the current image
because the 'buildroot' user is not sudoer (and there is no root
password), to do some quick testing.

However, it is very possible to become root in that image; just tell
docker to run as root (but we can't do that with the helper script,
granted):

    docker run -u 0:0 blabla....

You can even do so in an existing container (notice the container ID in
the prompt):

    # in one terminal:
    $ id -a
    uid=1000(ymorin) gid=1000(ymorin) ...
    $ ./utils/docker-run
    br-user@1057fdbbcb55:/some/path$ id -a
    uid=1000(br-user) gid=1000(br-user) ...

    # in another terminal:
    $ docker exec -t -i -u 0:0 1057fdbbcb55 /bin/sh
    # id -a
    uid=0(root) gid=0(root) ...

And if one needs something a litlle longer-lasting, here's a trivial
Dockerfile;

    $ cat foo/Dockerfile
    FROM registry.gitlab.com/buildroot.org/buildroot/base:20220206.1756
    USER 0:0
    $ docker build -t br-root foo
    $ docker rn --rm -ti br-root
    # id -a
    uid=0(root) gid=0(root) ...

Et voilà.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  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

Re: [Buildroot] Docker container for 2022.02.x release

[Quentin Schulz]

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? 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 hub.docker.com but have the Overview page state that this is 
pull-limited and recommend using the gitlab registry instead? 
https://hub.docker.com/r/buildroot/base

Cheers,
Quentin
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] Docker container for 2022.02.x release

[Christian Stewart via buildroot]

[-- Attachment #1.1: Type: text/plain, Size: 1383 bytes --]

I recommend using quay.io instead to avoid the rate limit.

Best,
Christian Stewart

On Wed, Aug 24, 2022, 9:20 AM Quentin Schulz <
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? 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 hub.docker.com but have the Overview page state that this is
> pull-limited and recommend using the gitlab registry instead?
> https://hub.docker.com/r/buildroot/base
>
> Cheers,
> Quentin
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
>

[-- Attachment #1.2: Type: text/html, Size: 2403 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] Docker container for 2022.02.x release

[Thierry GUIBERT]

[-- Attachment #1.1: Type: text/plain, Size: 2055 bytes --]

Hi,

I think the actual situation is the good one, except that external users 
can't pull images from the gitlab registry

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

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

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

Regards



On 25/08/2022 18:25, Christian Stewart wrote:
> I recommend using quay.io <http://quay.io> instead to avoid the rate 
> limit.
>
> Best,
> Christian Stewart
>
> On Wed, Aug 24, 2022, 9:20 AM Quentin Schulz 
> <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? 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 hub.docker.com <http://hub.docker.com> but have the
>     Overview page state that this is
>     pull-limited and recommend using the gitlab registry instead?
>     https://hub.docker.com/r/buildroot/base
>
>     Cheers,
>     Quentin
>     _______________________________________________
>     buildroot mailing list
>     buildroot@buildroot.org
>     https://lists.buildroot.org/mailman/listinfo/buildroot
>

[-- Attachment #1.2: Type: text/html, Size: 4399 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] Docker container for 2022.02.x release

[Yann E. MORIN]

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

Re: [Buildroot] Docker container for 2022.02.x release

[Thierry GUIBERT]

Since I could feel Yann tapping on my shoulder while telling "

Extended documentation is most welcome, though! :-)

" , there is a patch following this email ;)



On 25/08/2022 20:01, Yann E. MORIN wrote:
> 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
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot