From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 987F26DE0ED9 for ; Thu, 21 Nov 2019 14:16:21 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.398 X-Spam-Level: X-Spam-Status: No, score=0.398 tagged_above=-999 required=5 tests=[AWL=-0.254, SPF_NEUTRAL=0.652] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GkdUbPjKEKIW for ; Thu, 21 Nov 2019 14:16:20 -0800 (PST) Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34]) by arlo.cworth.org (Postfix) with ESMTP id 2E6A26DE0ED0 for ; Thu, 21 Nov 2019 14:16:20 -0800 (PST) Received: from guru.guru-group.fi (localhost [IPv6:::1]) by guru.guru-group.fi (Postfix) with ESMTP id 0465B10008E for ; Fri, 22 Nov 2019 00:16:18 +0200 (EET) From: Tomi Ollila To: notmuch@notmuchmail.org Subject: Re: Tests failing on master In-Reply-To: <87pnhqsmes.fsf@tethera.net> References: <87pnhqsmes.fsf@tethera.net> User-Agent: Notmuch/0.28.3+84~g41389bb (https://notmuchmail.org) Emacs/25.2.1 (x86_64-unknown-linux-gnu) X-Face: HhBM'cA~ MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Nov 2019 22:16:21 -0000 On Sun, Nov 17 2019, David Bremner wrote: > Yes, being root would break some of the tests, e.g. those that rely on > removing permissions to generate an error. Probably we should just > document that running the test suite as root is not supported? If > someone can explain a good reason to run as root (maybe some odd > auto-builder, the tests in question could probably be modified to do > something more extreme (e.g. delete a file) rather than chmod. Yes, rootless podman containers! if I run e.g $ podman run --rm -it -v $HOME:$HOME -w $HOME/vc/ext/notmuch \ notmuch-buildenv-debian10: /bin/zsh [root@e489c80816a9 notmuch]# id uid=0(root) gid=0(root) groups=0(root) [root@e489c80816a9 notmuch]# pwd /home/too/vc/ext/notmuch [root@e489c80816a9 build]# ls -l configure -rwxr-xr-x. 1 root root 41920 Nov 17 21:00 configure [root@e489c80816a9 build]# exit $ ls -l $HOME/vc/ext/notmuch/configure -rwxr-xr-x. 1 too too 41920 Nov 17 23:00 /home/too/vc/ext/notmuch/configure $ podman unshare cat /proc/self/uid_map 0 1000 1 1 100000 65536 The last line, would have had same results if run inside container, tells that uid 0 (root) inside container was mapped to uid 1000 (too) outside, on "host" side, and 1 uid was mapped, from uid 1 onwards in container, uids are mapped starting from 100000 outside. All that means, that I can do, without sudo, all kinds of things when using this container technology. Files owned by my uid outside container are seen as owned by root inside container. Since last spring, I've been gradually moving all things I used docker to podman. And everything has (in my use cases) worked better. In Fedora it just works (already). In Ubuntu 16.04 and RHEL 7.7 it also worked when I tried, but lack of fuse-overlayfs makes it slow (to start) in these systems. I hope every system in 2020 has good podman support... All that long text written, I can take care notmuch tests can be run on podman containers... > > cheers, > > d YEA, Tomi