public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: Antonin Godard <antonin.godard@bootlin.com>,
	Quentin Schulz <foss@0leil.net>,
	docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] tools/build-docs-container: make concurrent-safe
Date: Thu, 9 Oct 2025 12:07:16 +0200	[thread overview]
Message-ID: <3fce0896-3f41-452f-aa45-4d239dc2d5ff@cherry.de> (raw)
In-Reply-To: <DDDPDWQEDH3V.1L0AMHY2FAHEZ@bootlin.com>

On 10/9/25 12:01 PM, Antonin Godard wrote:
> On Thu Oct 9, 2025 at 10:59 AM CEST, Quentin Schulz wrote:
> [...]
>> The only downside is that we cannot infer from the image sha the
>> underlying distro we're testing.
> 
> Maybe we could retag the image after it is built and include the image name +
> the sha in the tag? With `$OCI tag source dest`, then `$OCI rmi source`?
> 

You would get one tag per run of the script, polluting your image tags.. 
I'm not sure it's worth it tbh.

We do get the output of podman build though which does print the FROM 
layer, c.f.:

tools/build-docs-container leap:15.6 html
Emulate Docker CLI using podman. Create /etc/containers/nodocker to 
quiet msg.
STEP 1/12: FROM docker.io/opensuse/leap:15.6

We can also add an echo somewhere to display what we're currently 
testing for example.

Quentin


      reply	other threads:[~2025-10-09 10:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-09  8:59 [PATCH] tools/build-docs-container: make concurrent-safe Quentin Schulz
2025-10-09  9:29 ` Quentin Schulz
2025-10-09 10:04   ` [docs] " Antonin Godard
2025-10-09 10:01 ` Antonin Godard
2025-10-09 10:07   ` Quentin Schulz [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=3fce0896-3f41-452f-aa45-4d239dc2d5ff@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=foss@0leil.net \
    /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