On Sat, Mar 07, 2020 at 05:56:43PM -0800, Noah Meyerhans wrote:
> > > So in case we'd be removing this dependency to satisfy your container
> > > use case (which is IMO very valid), we should carefully re-add a
> > > dependency on cloud-utils in our VM images.
> >
> > If I may add if it wasn't
On Sat, Mar 07, 2020 at 01:40:53AM +0100, Marco d'Itri wrote:
> Nowadays (since Debian 10) systemd can automatically grow file systems
> and swap partitions just by adding the x-systemd.growfs flag to fstab.
Thanks for letting us know.
I added the flag and as announced it works fine:
On Sun, Mar 08, 2020 at 02:49:26AM +0100, Thomas Goirand wrote:
> On 3/7/20 11:53 PM, Thomas Goirand wrote:
> > So in case we'd be removing this dependency to satisfy your container
> > use case (which is IMO very valid), we should carefully re-add a
> > dependency on cloud-utils in our VM images.
On 3/7/20 11:53 PM, Thomas Goirand wrote:
> So in case we'd be removing this dependency to satisfy your container
> use case (which is IMO very valid), we should carefully re-add a
> dependency on cloud-utils in our VM images.
If I may add if it wasn't obvious with what I wrote: our VM images
On 3/7/20 1:40 AM, Marco d'Itri wrote:
> Nowadays (since Debian 10) systemd can automatically grow file systems
> and swap partitions just by adding the x-systemd.growfs flag to fstab.
> This is also important because cloud-guest-utils depends on e2fsprogs,
> which is not needed in containers
Nowadays (since Debian 10) systemd can automatically grow file systems
and swap partitions just by adding the x-systemd.growfs flag to fstab.
This is also important because cloud-guest-utils depends on e2fsprogs,
which is not needed in containers and systems with XFS (which has been
the RHEL
