From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Ulrich Teichert <ulrich.teichert@ebs-group.io>,
Isar <isar-users@googlegroups.com>,
"MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
Cc: "krypton@ulrich-teichert.org" <krypton@ulrich-teichert.org>
Subject: Re: [PATCH 1/1] Feature: Allow customization inside the schroot-run
Date: Wed, 15 Jul 2026 12:25:31 +0200 [thread overview]
Message-ID: <6ae03c34-2114-44db-abe3-16b5745a5ebb@siemens.com> (raw)
In-Reply-To: <DB9PR08MB74482698562CD0BDF2CF6038C3F82@DB9PR08MB7448.eurprd08.prod.outlook.com>
On 15.07.26 11:19, 'Ulrich Teichert' via isar-users wrote:
> Hi Felix,
>
>> On Wed, 2026-07-15 at 06:54 +0000, 'Ulrich Teichert' via isar-users
>> wrote:
>>> Allow customization inside the schroot-run of image-tools-extension
>>> by introducing the variables IMAGER_SCHROOT_CMD (useful to inject
>>> a local apt-repository into the schroot), IMAGER_SCHROOT_UPDATE_OPTS
>>> (to add the sources list) and IMAGER_SCHROOT_INSTALL_OPTS (to inject
>>> options during install).
>
>> Hi,
>>
> I> would like to postpone this patch until "add support to build isar
>> unprivileged" is merged, as this splits the imager_run path into
>> schroot and unshare.
>
> That's fine with me.
>
>> Apart from that, I'm wondering if the change is really needed, as the
>> custom repo could also be injected into the whole build and by that
>> should also be accessible during imaging.
>
> Well, I am injecting the same repository with DISTRO_APT_SOURCES
> but accessing it during the schroot-run failed, so I simply re-injecting it.
> If the orginal setting could be preserved that would be nice, but I couldn't
> get it to work,
>
It's better to understand the root cause for the canonical approach
failing here.
Jan
--
Siemens AG, Foundational Technologies
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 visit https://groups.google.com/d/msgid/isar-users/6ae03c34-2114-44db-abe3-16b5745a5ebb%40siemens.com.
prev parent reply other threads:[~2026-07-15 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 6:54 'Ulrich Teichert' via isar-users
2026-07-15 8:14 ` 'MOESSBAUER, Felix' via isar-users
2026-07-15 9:19 ` 'Ulrich Teichert' via isar-users
2026-07-15 10:25 ` 'Jan Kiszka' via isar-users [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=6ae03c34-2114-44db-abe3-16b5745a5ebb@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=krypton@ulrich-teichert.org \
--cc=ulrich.teichert@ebs-group.io \
/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