From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6736062139219312640 X-Received: by 2002:adf:e410:: with SMTP id g16mr5201374wrm.297.1568367199885; Fri, 13 Sep 2019 02:33:19 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:adf:aacd:: with SMTP id i13ls104581wrc.3.gmail; Fri, 13 Sep 2019 02:33:19 -0700 (PDT) X-Google-Smtp-Source: APXvYqyER5REBw6OHo08N5QvhV9R+IU5lmUsd/DnFnhHXcBFb+6s0o9HIUlqewjzoJ2tZWrBH37Q X-Received: by 2002:a5d:4044:: with SMTP id w4mr40404146wrp.281.1568367199434; Fri, 13 Sep 2019 02:33:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568367199; cv=none; d=google.com; s=arc-20160816; b=O3zEG+tk0zdTVArmpJo0XDIfuM5n/Z4AJNfSttG6YV/JMYF4iK8vkfZMyPSoDoBuRM xKy6X2DBcyNM7BXRyLzRtwEQo5s3NVasQKT+fsrHBI/zjY9gBO27ELYRqa/JVv2pUUC2 M5oCscWOSN93tQRv03hUM4+yu4VEPsDIQTgb/b9GEa2yKiJBjehN4e6NVLdOT/y2FJzh +R3V4zPLTNsMOEe7gideKnkU6FT0lalX0DJuAEmV4qOp9y8G53A2fnLkdr/H7HVT8B5t yAE7SNrDGKrERKqJ6+zUkmyIGDwpJiqGK1LFL181tlpBNONGDJafGnadOrUbNv342KLm 4G9g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:to:from:date; bh=0apFcVRCY75nm4+uDeGjPD2YHeCJl7Z770Je4EBmiRw=; b=0PVSEZmhhCa+88H/LIW53RIX6M8G2OcZoAAaDcf7kCjogs6A2xLI9jXfX42gr5yocs xuV9BQ+V66MZ7dMQOhhqeX4edc53DjaMt52zNkf82Q65A5rOgG4qyhCZ+qup1yxWDaqS QtyXrEiiWVqMN/TYK3VlC/qYz0BcWyuVhuU6UdlLiKllSadqB88YmQ/9/jElKKpQJQ4D bcvTTpRHnJ+yivoDWHLBe4jkULN1vSuGcNjPYCLJkJ4OgBV+Yy63YkC78T//HGE692ts Xi+uUlHSB1KNQRPYnMky2xPdegQJIU6HS3ysCjVbKnbonnLWAtxSRJ1c0uobjweavIGT wMTw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id w8si120580wmk.1.2019.09.13.02.33.19 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 13 Sep 2019 02:33:19 -0700 (PDT) Received-SPF: neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Received: from yssyq.m.ilbers.de (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 x8D9XH2o023692 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Fri, 13 Sep 2019 11:33:18 +0200 Date: Fri, 13 Sep 2019 11:33:17 +0200 From: Baurzhan Ismagulov To: isar-users@googlegroups.com Subject: Re: fakechroot Message-ID: <20190913093317.GL6062@yssyq.m.ilbers.de> Mail-Followup-To: isar-users@googlegroups.com References: <87486b31-2560-1b78-6d7e-86bf10fc306f@siemens.com> <20190913081406.GJ6062@yssyq.m.ilbers.de> <8db6f5f1-8a36-768c-1b5d-0a0a3df866fb@siemens.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8db6f5f1-8a36-768c-1b5d-0a0a3df866fb@siemens.com> User-Agent: Mutt/1.10.1 (2018-07-13) 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: bAH9cFnkatkr On Fri, Sep 13, 2019 at 11:08:21AM +0200, Quirin Gylstorff wrote: > This was only an initial test but with fakechroot and fakeroot it should be > possible to have a non-priviledged debootstrap and chroot process. > > - Initial Creating with debootstrap did work. e.g.: > fakechroot fakeroot debootstrap buster amd64 > - what also work was using chroot to enter the create rootfs. > fakechroot chroot amd64 Thanks for sharing. That could be a welcome change. 1. How does fakechroot fakeroot perform privileged operations like chown, mknod, accessing other's files, mounting, etc.? We need that information to be consistent across multiple commands in multiple recipes (bootstrap, customize, install stuff, deploy, etc.). Wrapping one command is probably possible with any tool -- but currently I don't see how they could do what we need. Regarding keeping the information across multiple commands, Yocto's pseudo should allegedly be able to do that (not sure whether it keeps the state in a daemon or a file). Evaluating that was our next step (very low prio ATM) -- maybe that could be interesting for you as well. 2. fakechroot fakeroot is reported to work with foreign-arch chroots. Have you tried that? With kind regards, Baurzhan.