public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH 1/1] Use path in TMPDIR for schroot's overlay
Date: Tue, 12 Jul 2022 13:14:06 +0200	[thread overview]
Message-ID: <20220712111406.18449-2-ubely@ilbers.de> (raw)
In-Reply-To: <20220712111406.18449-1-ubely@ilbers.de>

By default, overlay path for schroot is /var/lib/schroot/union/overlay
that leads to the conflict with docker build.

Docker itself also uses overlayfs for the layers and we come to
situation with 'overlayfs over overlayfs' that is not supported
by the driver.

This solution places overlay path under the build/tmp so gitlab-runner
configuration changes or using external volumes in docker are not
required anymore.

Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
---
 meta/classes/sbuild.bbclass | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/classes/sbuild.bbclass b/meta/classes/sbuild.bbclass
index f9bfaaf6..405fb963 100644
--- a/meta/classes/sbuild.bbclass
+++ b/meta/classes/sbuild.bbclass
@@ -31,6 +31,7 @@ SCHROOT_CONF_FILE ?= "${SCHROOT_CONF}/chroot.d/${SBUILD_CHROOT}"
 SBUILD_CONFIG="${WORKDIR}/sbuild.conf"
 
 schroot_create_configs() {
+    mkdir -p "${TMPDIR}/schroot-overlay"
     sudo -s <<'EOSUDO'
         set -e
 
@@ -46,6 +47,7 @@ root-groups=root,sbuild
 source-root-users=${SCHROOT_USER}
 source-root-groups=root,sbuild
 union-type=overlay
+union-overlay-directory=${TMPDIR}/schroot-overlay
 preserve-environment=true
 EOF
 
-- 
2.20.1


  reply	other threads:[~2022-07-12 11:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 11:14 [PATCH 0/1] " Uladzimir Bely
2022-07-12 11:14 ` Uladzimir Bely [this message]
2022-07-19 15:27   ` [PATCH 1/1] " Michael Adler
2022-07-20  5:48 ` [PATCH 0/1] " Anton Mikanovich

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=20220712111406.18449-2-ubely@ilbers.de \
    --to=ubely@ilbers.de \
    --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