From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7115329314959130624 X-Received: by 2002:a05:6512:3f84:b0:47f:673c:31b7 with SMTP id x4-20020a0565123f8400b0047f673c31b7mr9836291lfa.473.1656677320779; Fri, 01 Jul 2022 05:08:40 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:6512:238e:b0:481:2fa:2826 with SMTP id c14-20020a056512238e00b0048102fa2826ls20558lfv.0.gmail; Fri, 01 Jul 2022 05:08:39 -0700 (PDT) X-Google-Smtp-Source: AGRyM1vqYhZzDHWeiltKJNNJ6uqNrCH7znzuLo0AZoSsLmYb26noQ/uQ5+wNXC/+w062N+fl457a X-Received: by 2002:a05:6512:4012:b0:47f:641d:45a4 with SMTP id br18-20020a056512401200b0047f641d45a4mr8490496lfb.425.1656677319731; Fri, 01 Jul 2022 05:08:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656677319; cv=none; d=google.com; s=arc-20160816; b=jR4v7NxqwxwkpDyUe5REU08Nn55NnLIVkyG7V0clzdypoCn9a9paQEbj2eLyhI1feh 3ug5nruISoDm75tFama+oDEm402DzFeu0rDcL8cPbdn5+33yjHBUcr+Vfv0Lxluckz+t +WtOsFZvhfEbZi6aNRV5fc4+oO4jdXnkF4lDA6a0KesN0IZ0uM4+JkuCTtXv/PSz1suF 5DsEYgFTmUae4e+TLHOKFvTZtBUK0qmWmublgXaGgEonEh/mput0JTIqMV8hPGsXx1BR dXDnEGr49qwOYHSTOGL51WPnXZK0GDi/nqRoEotW9gndm3uBMv1j3mUeWA3wKDBOVN6L qrhQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id; bh=Ubto3Mu/VPAlSdhxbC17YowdrS4Nlr+u1D7BxjZZy8w=; b=uX2mDmnffPPPun3BOZCUxgD1ninUeUljGmWr3z+3yUXSEjbRSpCSPb7hsZrBwz81o2 jYKSUGOCbgxym5CoXM8X/kUFn+xtHSAvBH2F1LCyrAjjVvWHGJBeHIOrESWlzipkxizE Y9t5IGxSjf24U+bQj3Kb3uc8prGk3Jm7hN2LW3Ab+qrlRVYjDDRZxKHhIF+ROq/03ows J1G7BwoXtjr/axLETsi5+bMLVM4ehsx59nx5JLDtxiF1qnwXAwabCilnNUQiySmzFZDH i0fnS94z2BJD+yzhv2pTN32XDMB/SRcEosW2ys3YRmqdQtT1Z5lq63ZX0jjmJfaLuTBs 5gzw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of amikan@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=amikan@ilbers.de Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id bj25-20020a2eaa99000000b0024da01a8c6dsi778892ljb.1.2022.07.01.05.08.39 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Fri, 01 Jul 2022 05:08:39 -0700 (PDT) Received-SPF: pass (google.com: domain of amikan@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 amikan@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=amikan@ilbers.de Received: from [127.0.0.1] (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+deb9u1) with ESMTPSA id 261C8bhE015659 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 1 Jul 2022 14:08:38 +0200 Message-ID: <198f52fb-c71e-7dea-8736-7443487a6bd8@ilbers.de> Date: Fri, 1 Jul 2022 15:08:37 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 Subject: Re: ISAR schroot mountpoints when running in container Content-Language: en-US To: "Moessbauer, Felix" , "isar-users@googlegroups.com" Cc: "jan.kiszka@siemens.com" , "Bezdeka, Florian" , "ubely@ilbers.de" , "Schmidt, Adriaan" References: <2595591.lGaqSPkdTl@home> <34a96a67d430b37f36892cf2c5cc9b5922655562.camel@siemens.com> <88c61c25-40d7-3b02-3b9d-40cf459c7edb@siemens.com> From: Anton Mikanovich In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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: 0cxMUL3zOf+6 01.07.2022 14:30, Moessbauer, Felix wrote: > Required changes: > > In ISAR, we have to make the name of the Schroot folder more unique. But as BB requires recipes to be deterministic (per-build), we have to inject the ID from the outside. This could happen either via local.conf or via an env-var. This env-var has to be provided by KAS, with an fallback in ISAR to use the PID of the bitbake process if not provided. > > A probably better strategy would be to get a per-bitbake invocation constant UUID directly from Bitbake. Don't know if that already exists in BB. > Putting Adriaan in CC. > > Felix Hello, I've already proposed unique per-build ID generation in '[PATCH 2/6] base: Implement bitbake build ID'. Not sure it suits mentioned requirements, but can be good starting point.