public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "Bezdeka, Florian" <florian.bezdeka@siemens.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"kas-devel@googlegroups.com" <kas-devel@googlegroups.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:36:42 +0000	[thread overview]
Message-ID: <AM9PR10MB4869048746C1692AFA9EE8BA89BD9@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <8ab14ecf557ff6412fa2d740f59e2b99a638e6a7.camel@siemens.com>

> -----Original Message-----
> From: Bezdeka, Florian (T CED SES-DE) <florian.bezdeka@siemens.com>
> Sent: Friday, July 1, 2022 11:28 AM
> To: isar-users@googlegroups.com; kas-devel@googlegroups.com; Moessbauer,
> Felix (T CED SES-DE) <felix.moessbauer@siemens.com>
> Cc: Bossert, Andre (DI FA CTR SVC PRC2) <andre.bossert@siemens.com>; Kiszka,
> Jan (T CED) <jan.kiszka@siemens.com>; Schild, Henning (T CED SES-DE)
> <henning.schild@siemens.com>
> Subject: Re: ISAR schroot mountpoints when running in container
> 
> 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)?

The question boils down to "can this mountpoint safely be shared across ISAR runs", and this should be possible.
We run this code for a while and never experienced any sharing issues.

The schroots also have a PID component in their name. [1]
But I'm not 100% sure that the PIDs in the privileged container are unique across all containers.
At least for non-privileged containers you have local-only PIDs (or better, a local PID namespace).

Felix

[1] https://github.com/ilbers/isar/blob/next/meta/classes/sbuild.bbclass#L26

> 
> >
> > 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
> >


  reply	other threads:[~2022-07-01  9:36 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
2022-07-01  9:36   ` Moessbauer, Felix [this message]
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=AM9PR10MB4869048746C1692AFA9EE8BA89BD9@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM \
    --to=felix.moessbauer@siemens.com \
    --cc=andre.bossert@siemens.com \
    --cc=florian.bezdeka@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