launchpad-users team mailing list archive
-
launchpad-users team
-
Mailing list archive
-
Message #07118
Re: Launchpad builder VMs upgraded to bionic
-
To:
Dimitri John Ledkov <xnox@xxxxxxxxxx>
-
From:
Colin Watson <cjwatson@xxxxxxxxxxxxx>
-
Date:
Wed, 16 Sep 2020 11:35:06 +0100
-
Cc:
Eric Desrochers <eric.desrochers@xxxxxxxxxxxxx>, Ubuntu Developers <ubuntu-devel@xxxxxxxxxxxxxxxx>, Guilherme Piccoli <gpiccoli@xxxxxxxxxxxxx>, Mauricio Faria de Oliveira <mfo@xxxxxxxxxxxxx>, Steve Langasek <steve.langasek@xxxxxxxxxx>, launchpad-users@xxxxxxxxxxxxxxxxxxx
-
In-reply-to:
<CANBHLUhQd9Zddo-SZhndt-7Gjaeg8MVba+82Ks6nbxfH=fRdBA@mail.gmail.com>
-
Mail-followup-to:
Dimitri John Ledkov <xnox@xxxxxxxxxx>, Steve Langasek <steve.langasek@xxxxxxxxxx>, Guilherme Piccoli <gpiccoli@xxxxxxxxxxxxx>, Mauricio Faria de Oliveira <mfo@xxxxxxxxxxxxx>, Ubuntu Developers <ubuntu-devel@xxxxxxxxxxxxxxxx>, Eric Desrochers <eric.desrochers@xxxxxxxxxxxxx>, launchpad-users@xxxxxxxxxxxxxxxxxxx
-
User-agent:
Mutt/1.10.1 (2018-07-13)
On Wed, Sep 16, 2020 at 10:22:05AM +0100, Dimitri John Ledkov wrote:
> chroot builders do call ~= `sudo chroot` at some point.
The main work is done by sbuild, which uses schroot, not "sudo chroot".
(We used to use sbuild's sudo session mode, but I changed that to
schroot in 2017.)
> would changing limits.d + adding pam_limits to sudo pam config be
> enough for launchpad-buildd?
I think schroot does support PAM. However, I don't think it's good
design for launchpad-buildd to rely on PAM, since after all it's not
doing any kind of interactive authentication. I would rather not pursue
this option any further. There are other less complicated ways to set
resource limits.
--
Colin Watson (he/him) [cjwatson@xxxxxxxxxxxxx]
Follow ups
References