From: "Bezdeka, Florian" <florian.bezdeka@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"kas-devel@googlegroups.com" <kas-devel@googlegroups.com>,
"Moessbauer, Felix" <felix.moessbauer@siemens.com>
Cc: "Bossert, Andre" <andre.bossert@siemens.com>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
"Schild, Henning" <henning.schild@siemens.com>
Subject: Re: ISAR schroot mountpoints when running in container
Date: Fri, 1 Jul 2022 09:27:48 +0000 [thread overview]
Message-ID: <8ab14ecf557ff6412fa2d740f59e2b99a638e6a7.camel@siemens.com> (raw)
In-Reply-To: <AM9PR10MB4869B14333649ECE141675F689BD9@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM>
On Fri, 2022-07-01 at 09:11 +0000, Moessbauer, Felix wrote:
> Hi,
>
> as we now have sbuild in ISAR next, first users stumble upon issues
> when running the kas docker image in the gitlab-ci.
> This requires additional mountpoints, as the schroot itself uses
> overlayfs and stacking two overlayfs is not possible.
> By that, you have to mount the overlay from the host.
>
> The kas-container script already has support for that, but it lacks
> documentation on how to configure this manually.
> In short: The following mountpoint has to be added (as RW):
> /var/lib/schroot/union/overlay
So you added this mount point to your gitlab runner configuration? If
so, can this mount (safely) be shared between multiple gitlab build
jobs (running at the same time)?
>
> As this is neither an ISAR issue, nor a KAS issue per-se, I send this
> to both lists.
>
> Felix
> --
> Siemens AG, Linux Expert Center
> Otto-Hahn-Ring 6, 81739 München, Germany
>
next prev parent reply other threads:[~2022-07-01 9:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 9:11 Moessbauer, Felix
2022-07-01 9:27 ` Bezdeka, Florian [this message]
2022-07-01 9:36 ` Moessbauer, Felix
2022-07-01 10:05 ` Bezdeka, Florian
2022-07-01 10:23 ` Uladzimir Bely
2022-07-01 10:30 ` Bezdeka, Florian
2022-07-01 10:43 ` Jan Kiszka
2022-07-01 11:30 ` Moessbauer, Felix
2022-07-01 11:38 ` Henning Schild
2022-07-01 11:48 ` Bezdeka, Florian
2022-07-01 12:08 ` Anton Mikanovich
2022-07-01 12:25 ` Moessbauer, Felix
2022-07-01 15:07 ` Gylstorff Quirin
2022-07-05 13:40 ` Moessbauer, Felix
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=8ab14ecf557ff6412fa2d740f59e2b99a638e6a7.camel@siemens.com \
--to=florian.bezdeka@siemens.com \
--cc=andre.bossert@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=kas-devel@googlegroups.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