From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: isar-users@googlegroups.com
Cc: Henning Schild <henning.schild@siemens.com>
Subject: Re: [PATCH v7 5/6] meta-isar: install expand-on-first-boot in most images and add space
Date: Fri, 23 Dec 2022 16:43:18 +0100 [thread overview]
Message-ID: <CAJGKYO5iU9CehYHAHfp-zqXctr+GVFGxo+bcCL89sezsmty=og@mail.gmail.com> (raw)
In-Reply-To: <20221223085529.8835-6-henning.schild@siemens.com>
On Fri, 23 Dec 2022 at 09:55, Henning Schild <henning.schild@siemens.com> wrote:
>
> Here we take the most common and generic images and add some empty space
> at the end of then.
> This will enable better interactive use of our example images since
> people will have some space to install some more packages. While the
> space seems fixed it really is open end if the mass storage happens to be
> bigger, because we install expand-on-first-boot as well.
[...]
> +++ b/meta-isar/scripts/lib/wic/canned-wks/expand-padding.wks.inc
> @@ -0,0 +1,5 @@
> +# some extra space we put in the end after the last partition
> +# that allows testing expand-on-first-boot while at the same time
> +# making our images more useful because they have space to play around
> +
> +part --source empty --no-table --ondisk sda --size 256M
This approach works only if the expand last partition is installed and
works but only after the first boot into a device or a virtual
machine.
Otherwise this space will remain unavailable. For example, if someone
chroot into wic image for applying some changes s/he wants to test
before integrating into a recipe.
An alternative to add extra space into the disk, is to add it directly
into the rootfs with these two last options:
part / --source rootfs [...] --extra-space 1G --overhead-factor 1.2
I developed wicshell.sh in order to automatize the operations of
chroot into the .wic image and also sharing a folder with the host
which is always useful when ssh/scp is not available.
https://github.com/robang74/isar-nvidia-debian/blob/main/wicshell.sh
Moreover, I saw that there are .conf files for producing vmdk and ova
files. IMHO, a more general and flexible approach is to create these
files directly from the .wic image, like in my project
wicinst vmdk:$filename.vmdk [disk_size_in_gigabytes]
wicinst ovaf:$filename.ova [disk_size_in_gigabytes]
https://github.com/robang74/isar-nvidia-debian/blob/main/wicinst.sh
I hope you are going to take in consideration this approach to
simplify the access of these functionalities which are documented into
my project README.md
Every suggestion and critic in order to improve this approach will be welcome.
Best regards, R-
next prev parent reply other threads:[~2022-12-23 15:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 8:55 [PATCH v7 0/6] expand-on-first-boot btrfs and CI testing Henning Schild
2022-12-23 8:55 ` [PATCH v7 1/6] expand-on-first-boot: really only do that once, especially on failure Henning Schild
2022-12-23 8:55 ` [PATCH v7 2/6] expand-on-first-boot: support resizing a btrfs Henning Schild
2022-12-23 8:55 ` [PATCH v7 3/6] meta-isar: introduce an example to use btrfs Henning Schild
2022-12-23 8:55 ` [PATCH v7 4/6] CI: improve cibuilder readability Henning Schild
2022-12-23 8:55 ` [PATCH v7 5/6] meta-isar: install expand-on-first-boot in most images and add space Henning Schild
2022-12-23 15:43 ` Roberto A. Foglietta [this message]
2022-12-23 19:11 ` Roberto A. Foglietta
2022-12-23 8:55 ` [PATCH v7 6/6] CI: expect a message about filesystem resize vom expand script Henning Schild
2022-12-23 9:07 ` [PATCH v7 0/6] expand-on-first-boot btrfs and CI testing Henning Schild
2022-12-30 19:18 ` Anton Mikanovich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJGKYO5iU9CehYHAHfp-zqXctr+GVFGxo+bcCL89sezsmty=og@mail.gmail.com' \
--to=roberto.foglietta@gmail.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox