Launchpad builder VMs upgraded to bionic
Dimitri John Ledkov
xnox at ubuntu.com
Wed Sep 16 09:22:05 UTC 2020
On Wed, 9 Sep 2020 at 23:25, Steve Langasek <steve.langasek at ubuntu.com> wrote:
> On Wed, Sep 09, 2020 at 10:33:00AM +0100, Dimitri John Ledkov wrote:
> > > Failing that, can somebody advise on whether there's an appropriate way
> > > to configure this in an image without having to maintain a fork of
> > > systemd? The workflow here is that we consume Ubuntu cloud images and
> > > make a few small changes to them, mostly things like installing
> > > launchpad-buildd, before publishing them to Glance for use when starting
> > > new builder VMs.
> > I have not tried this, but i think one should be able to create a
> > snippet in /etc/security/limits.d/ with like
> > * soft memlock unlimited
> > * hard memlock unlimited
> > Or to the appropriate value of 64*1024 instead of unlimited.
> Which should only take effect for things which are part of PAM sessions that
> have invoked pam_limits. I don't think this would be true for the builders?
chroot builders do call ~= `sudo chroot` at some point. But looking at
pam configs, sudo doesn't invoke pam_limits (which is interesting,
because su does)
would changing limits.d + adding pam_limits to sudo pam config be
enough for launchpad-buildd?
More information about the ubuntu-devel