All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry GUIBERT via buildroot <buildroot@buildroot.org>
To: yann.morin.1998@free.fr, thomas.petazzoni@bootlin.com,
	buildroot@buildroot.org
Cc: Thierry GUIBERT <thierry.guibert@croix-rouge.fr>
Subject: [Buildroot] [PATCH] Add documentation about docker registry
Date: Sun,  4 Sep 2022 15:46:13 +0200	[thread overview]
Message-ID: <20220904134613.31886-1-thierry.guibert@croix-rouge.fr> (raw)

Signed-off-by: Thierry GUIBERT <thierry.guibert@croix-rouge.fr>
---
 docs/manual/adding-board-support.txt | 19 ++++++++++++++++---
 1 file changed, 16 insertions(+), 3 deletions(-)

diff --git a/docs/manual/adding-board-support.txt b/docs/manual/adding-board-support.txt
index cd90a5871f..f68e192468 100644
--- a/docs/manual/adding-board-support.txt
+++ b/docs/manual/adding-board-support.txt
@@ -48,9 +48,22 @@ and configurations in these directories, and reference them from the main
 Buildroot configuration. Refer to xref:customize[] for more details.
 
 Before submitting patches for new boards it is recommended to test it by
-building it using latest gitlab-CI docker container. To do this use
-utils/docker-run script and inside it issue these commands:
+building it using latest gitlab-CI docker container. 
+To do this use utils/docker-run script and inside it issue these commands:
 --------------------
- $ make +<boardname>_defconfig+
+ $ make <boardname>_defconfig
  $ make
 --------------------
+
+By defaut, buildroot developpers use our gitlab.com registry and it should
+be convenient for most usages. 
+If you still want to build your own docker images :
+--------------------
+ $ DOCKER_REGISTRY=registry.gitlab.com
+ $ IMAGE_NAME=buildroot.org/buildroot/base
+ $ IMAGE_TAG=YYYYMMDD.HHMM
+ $ docker build  --pull --no-cache \
+	-t ${DOCKER_REGISTRY}/${IMAGE_NAME}:${IMAGE_TAG} support/docker
+ $ docker push ${DOCKER_REGISTRY}/${IMAGE_NAME}:${IMAGE_TAG}
+--------------------
+
-- 
2.37.2

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

             reply	other threads:[~2022-09-04 13:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-04 13:46 Thierry GUIBERT via buildroot [this message]
2023-04-16 12:36 ` [Buildroot] [PATCH] Add documentation about docker registry Yann E. MORIN

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=20220904134613.31886-1-thierry.guibert@croix-rouge.fr \
    --to=buildroot@buildroot.org \
    --cc=thierry.guibert@croix-rouge.fr \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.