public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"Moessbauer, Felix" <felix.moessbauer@siemens.com>
Subject: Re: ISAR schroot mountpoints when running in container
Date: Fri, 01 Jul 2022 13:23:33 +0300	[thread overview]
Message-ID: <2595591.lGaqSPkdTl@home> (raw)
In-Reply-To: <AM9PR10MB4869B14333649ECE141675F689BD9@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM>

In the email from Friday, 1 July 2022 12:11:42 +03 user 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
> 
> As this is neither an ISAR issue, nor a KAS issue per-se, I send this to
> both lists.
> 

Hello.

Yes, this overlayfs-over-overlayfs issue can be solved by something like 

`volumes = ["/path/to/overlay:/var/lib/schroot/union/overlay"]`

placed to `/etc/gitlab-runner/config.toml`, as mentioned in 'sbuild' series 
cover-letter



> Felix
> --
> Siemens AG, Linux Expert Center
> Otto-Hahn-Ring 6, 81739 München, Germany


-- 
Uladzimir Bely




  parent reply	other threads:[~2022-07-01 10:23 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
2022-07-01 10:05     ` Bezdeka, Florian
2022-07-01 10:23 ` Uladzimir Bely [this message]
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=2595591.lGaqSPkdTl@home \
    --to=ubely@ilbers.de \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@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