public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Florian Bezdeka <florian.bezdeka@siemens.com>,
	isar-users <isar-users@googlegroups.com>
Cc: "Cirujano-Cuesta, Silvano" <silvano.cirujano-cuesta@siemens.com>,
	Quirin Gylstorff <quirin.gylstorff@siemens.com>,
	"Moessbauer, Felix (T CED SES-DE)" <felix.moessbauer@siemens.com>
Subject: Re: [RFC][PATCH 1/3] Introduce fetcher from container registries
Date: Wed, 10 Jul 2024 13:08:14 +0200	[thread overview]
Message-ID: <1f6eb7b8-7443-4f9b-bafe-4cfed5c6de41@siemens.com> (raw)
In-Reply-To: <41792a6ebde246fd404a4df825ab04a8a7a26588.camel@siemens.com>

On 10.07.24 09:55, Florian Bezdeka wrote:
> On Tue, 2024-07-09 at 19:31 +0200, 'Jan Kiszka' via isar-users wrote:
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> This bitbake fetcher allows to pull container images from registries,
>> store them in the download cache and transfer them into the workdir of
>> recipes requesting the image. The format of the URL is
>>
>> docker://[<host>/]<image>;digest=sha256:...[;tag=<tag>]
> 
> The schema - docker:// - is defined by / required by skopeo below,
> right? 
> 
> Would it be possible to use something like container:// to avoid the
> product name in all the user recipes?
> 

I'm re-using skopeo's schema here, right:

https://manpages.debian.org/bookworm/skopeo/skopeo.1.en.html

It would be technically possible to use container:// instead or as well
and translate that internally. But would that really be helpful / intuitive?

Jan

-- 
Siemens AG, Technology
Linux Expert Center

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/1f6eb7b8-7443-4f9b-bafe-4cfed5c6de41%40siemens.com.

  reply	other threads:[~2024-07-10 11:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09 17:31 [RFC][PATCH 0/3] Introduce container fetcher and pre-loader 'Jan Kiszka' via isar-users
2024-07-09 17:31 ` [RFC][PATCH 1/3] Introduce fetcher from container registries 'Jan Kiszka' via isar-users
2024-07-10  7:55   ` 'Florian Bezdeka' via isar-users
2024-07-10 11:08     ` 'Jan Kiszka' via isar-users [this message]
2024-07-09 17:31 ` [RFC][PATCH 2/3] container-loader: Introduce helper to load container images into local registry 'Jan Kiszka' via isar-users
2024-07-10 12:46   ` 'MOESSBAUER, Felix' via isar-users
2024-07-10 16:20     ` 'Jan Kiszka' via isar-users
2024-07-12  9:19   ` 'Niedermayr, BENEDIKT' via isar-users
2024-07-12 13:45     ` 'Jan Kiszka' via isar-users
2024-07-12 12:11   ` 'Niedermayr, BENEDIKT' via isar-users
2024-07-12 13:49     ` 'Jan Kiszka' via isar-users
2024-07-09 17:31 ` [RFC][PATCH 3/3] meta-isar: Add demo packages for installing prebuilt containers 'Jan Kiszka' via isar-users

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=1f6eb7b8-7443-4f9b-bafe-4cfed5c6de41@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=florian.bezdeka@siemens.com \
    --cc=jan.kiszka@siemens.com \
    --cc=quirin.gylstorff@siemens.com \
    --cc=silvano.cirujano-cuesta@siemens.com \
    /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