Hello, On Fri 08 Aug 2025 at 08:20pm +02, Christoph Biedl wrote:
> Sean Whitton wrote... > >> /etc/schroot/sbuild/fstab contains this: >> >> # Mount a large scratch space for the build, so we don't use up >> # space on an LVM snapshot of the chroot itself. >> /var/lib/sbuild/build /build none rw,bind 0 0 > (...) > >> I would suggest that these lines be removed from the default >> /etc/schroot/sbuild/fstab. Another possibility would be to mount a >> tmpfs there, but maybe that should be left to the local administrator. > > At a quick glance, both suggestion don't feel right. Especially when the > build creates a lot of data there. > > Just removing that line means the chroot may just run full, depending on > the backend and other configurations. Using tmpfs may likewise trigger > OOM situations. > > The only sensible solution I can think of here was schroot will do the > job sbuild no longer wants to do: Create a temporary directory in that > scratch space, mount it to /build inside, and clean up afterwards. This > however can no longer be achieved using an fstab line. > > This requires some more checking. Your thoughts? As you mention, it is difficult to think about it because there are so many possible configurations for schroots. The solution you propose means maintaining most of the assumptions made by the approach implemented by the fstab line. Therefore it seems least likely to introduce problems for users. So, I agree. Thank you for thinking it through. -- Sean Whitton
signature.asc
Description: PGP signature
