[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#976073: sbuild: support "podman" as chroot mode and provide a sbuild-create-oci command (built on top of buildah)



Control: clone -1 -2
Control: reassign -2 autopkgtest
Control: retitle -2 "autopkgtest: implement a podman backend"
Control: block -1 by -2

Hi,

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.

> 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?

Bonus point: adding this to autopkgtest means contributing Python code
instead of Perl. ;-)

Cheers,
-- 
  ⢀⣴⠾⠻⢶⣦⠀   Raphaël Hertzog <hertzog@debian.org>
  ⣾⠁⢠⠒⠀⣿⡁
  ⢿⡄⠘⠷⠚⠋    The Debian Handbook: https://debian-handbook.info/get/
  ⠈⠳⣄⠀⠀⠀⠀   Debian Long Term Support: https://deb.li/LTS


Reply to: