Hi, Quoting Raphael Hertzog (2020-11-29 15:24:01) > On Sun, 29 Nov 2020, Johannes Schauer Marin Rodrigues wrote: > > The resulting tarball can then be used with the sbuild unshare backend. The > > only time you need be root is to execute > > > > $ sudo sysctl -w kernel.unprivileged_userns_clone=1 > > > > But I guess you also need this for podman and buildah? > > Yes. it seems though there is progress: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898446 > > I'm absolutely for it! If somebody wants to implement and maintain it, > > please send patches for me to review. The person can then keep maintaining > > the podman chroot mode easily because sbuild is in the Debian group on > > salsa. > > > > What I would like even more, would be to add a podman backend to autopkgtest. > > This has the following advantages: > > > > - it would already work with sbuild today (no changes in sbuild required) > > - no duplicated work to have podman support in both sbuild and autopkgtest > > Even better indeed, but some official way to build the container would > also be welcome... would that also be best done in autopkgtest with > a new autopkgtest-build-podman command? > > Is the expectation that sbuild will use whatever "image/container/chroot" > is created by the respective autopkgtest-build-<backend> command? Or has > sbuild special requirements at this level? In general, sbuild should be fine with any chroot containing Essential:yes and apt. Starting from this, it will install all the stuff it needs like build-essential and so on. Admittedly this features is not tested much, so if you find a minimal chroot sbuild is not able to copy with, please file a bug, so that sbuild adds a few more bits of setup. Thanks! cheers, josch
Attachment:
signature.asc
Description: signature