Re: Publishing raw generic{,cloud} images without tar, and without compression, plus versionning of point releases
On 6/6/20 1:16 PM, Thomas Lange wrote:
>>>>>> On Sat, 6 Jun 2020 12:28:00 +0200, Bastian Blank <waldi@debian.org> said:
>
> > Also we don't want to specify the size a priori, because it can break to
> > easily. So we need to deduct the size during the build process.
> I could improve fai-diskimage using what zigo is using in his
> build-openstack-debian-image script. Call resize2fs, parted and
> truncate to make the fs and raw image as small as possible and add a
> few MB of additional space. That way we always will get the smallest
> image.
Thomas,
It'd be really great if you could implement this. I tried quickly to do
that on images produced by the team, but also failed quickly and gave up
quickly too! :)
> But I'm not sure if the partition hooks Bastian wrote
> may cause problems. I guess not, because we only have to resize
> partition 1 which is always at the end of the raw disk.
Cloud-init takes care of resizing when time image boots, so it's safe to
have a smaller image. We still need a bit of free space to allow:
- the resize itself
- the VM to boot while the resize isn't finished
Cheers,
Thomas Goirand (zigo)
Reply to:
- Prev by Date:
Re: Publishing raw generic{,cloud} images without tar, and without compression, plus versionning of point releases
- Next by Date:
Re: Publishing raw generic{,cloud} images without tar, and without compression, plus versionning of point releases
- Previous by thread:
Re: Publishing raw generic{,cloud} images without tar, and without compression, plus versionning of point releases
- Next by thread:
Re: Publishing raw generic{,cloud} images without tar, and without compression, plus versionning of point releases
- Index(es):