From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7032253102499561472 X-Received: by 2002:a05:6512:104b:: with SMTP id c11mr30673306lfb.115.1637931468703; Fri, 26 Nov 2021 04:57:48 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:6512:2610:: with SMTP id bt16ls74469lfb.2.gmail; Fri, 26 Nov 2021 04:57:47 -0800 (PST) X-Google-Smtp-Source: ABdhPJyvkRIFmHyYE5cce0WOpowvrfBRDyCKGQc85E1QbtKdmQ4XbfNGNjLpbndBnSg6oC4emD/y X-Received: by 2002:ac2:4423:: with SMTP id w3mr30292827lfl.385.1637931467484; Fri, 26 Nov 2021 04:57:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1637931467; cv=none; d=google.com; s=arc-20160816; b=Oxp5c54JCgDpoLx/qf2WotGxsuhmTxp0lkLkvlfr1Avm6jDyz1Ie+QE6qh/afa/6pr RmFaa0B41CV/BLyc3nSPOqhcD/NqwT/NNduElokvBodySPrU2CKU2aPM9OAwxiwvO8+g eVTW2sHb5SmG+csUv2qYVlMMoWquE1JEizL1dY/Qsbq4XKFJaYGGK+0Y0yjuAPQj9r+H OGEKh/IQGyrq8CoJEzP+GzDja7B1LvvmysUxI4eiLe89vuiO2hwcuIPBLhRCurgsFYEu o/fHi5Xxzh//T2/04Pk4dxDOsUdJzzWbiBpzm4DgzZKh561D2TenLhoyAfyFuoG1Wt0r jWCw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from; bh=dhDvTGYZ6qbm588zIgOwmfp2SFMkRiW+xPZ/A/3Yhis=; b=ntbQ8spFThN+NZJXkho3bfVT9S4KDyvpr5AQMXkSNK+8c3Mppe1J8j3Vnj6kAgi/Yd 0hFeswagmvG/7dzw3RdC4se36sUUXA31m9vO4ti/qUQE12RDfQCfNGQK+EZU+7b/OPzN pZQ1OMA2KSL5VQkehhD51ytl8D2a5PcVN3e69oNl0SY2zXCxZp/3BhT+C5nY/QVnKsCC 6sEJm/jHyUf+Xj04HA1dJCSBz/h5exlVM92bMSVCtBDyv/aX/1fBAp78Hj0Yz5hDOA0X fuCnP9RGDeyGmSxCKkiVwTPrRHv3lDugk7zR4IH0gXjLUYQdZ4lEZqHppuloOVbGwlVQ n/dQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of ubely@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=ubely@ilbers.de Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id e19si605104lfr.9.2021.11.26.04.57.47 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Fri, 26 Nov 2021 04:57:47 -0800 (PST) Received-SPF: pass (google.com: domain of ubely@ilbers.de designates 85.214.156.166 as permitted sender) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of ubely@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=ubely@ilbers.de Received: from hp.localnet (host-80-81-17-52.static.customer.m-online.net [80.81.17.52]) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPSA id 1AQCvjW1023328 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 26 Nov 2021 13:57:46 +0100 From: Uladzimir Bely To: Michael Adler Cc: isar-users@googlegroups.com Subject: Re: [PATCH v2 00/24] Sbuild/Schroot migration Date: Fri, 26 Nov 2021 15:57:17 +0300 Message-ID: <18620765.fSG56mABFh@hp> In-Reply-To: <20211126120921.vjpxnzbdfk4e6rr3@kratos> References: <20211119121333.13805-1-ubely@ilbers.de> <2071114.yiUUSuA9gR@home> <20211126120921.vjpxnzbdfk4e6rr3@kratos> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: /Naib53od/rr In mail from Friday, 26 Nov 2021. 15:09:21 +03 user Michael Adler wrote: > Hi Uladzimir, > > > It seems there is no way to say gitlab using external volume via the > > configuration file `.gitlab-ci.yml` > yes, because it is not universally applicable: there are various runner > implementations [1] and the "volumes" feature is not supported by every > runner (e.g. SSH-based). > > For CIP, we use custom Kubernetes runners. Although it is possible to setup > custom volumes [2], that's only half of the story: the other half is to > ensure that these directories actually exist on the host, which in the case > of gitlab-cloud-ci [3] (used by CIP and Siemens) are ephemeral, i.e. they > are dynamically created and destroyed based on on the CI workload. It > should be possible to support such volumes but it's definitely extra > engineering/maintenance effort. > > > So, gitlab will use external ("/m/ws-10/schroot-10a/union") directory on > > host. > What happens if I choose not to provide such a volume? Is it mandatory for > the build? Do I also need this for local containerized builds? > As I wrote, the problem that docker uses overlayfs to produce a working chroot. So, /var/lib/schroot/union/ happens to be on overlayfs. Sbuild also uses overlayfs - it mounts rootfs to /var/lib/schroot/union/underlay (as a lower, read-only layer) and uses /var/lib/schroot/union/overlay/ handle rw layer. But, it is not supported by overlayfs (owerdir=/lower,upperdir=/ upper,workdir=/work) when upperdir is on overlayfs (from docker). > > Kind regards, > Michael > > [1] https://docs.gitlab.com/runner/executors/ > [2] https://docs.gitlab.com/runner/executors/kubernetes.html#using-volumes > [3] https://gitlab.com/cip-project/cip-testing/gitlab-cloud-ci -- Uladzimir Bely Promwad Ltd. External service provider of ilbers GmbH Maria-Merian-Str. 8 85521 Ottobrunn, Germany +49 (89) 122 67 24-0 Commercial register Munich, HRB 214197 General Manager: Baurzhan Ismagulov