bare minimum disk space required for installation is not documented

[bam80]

The installation page doesn't have this info.

It's essential when you try to install to VM, for example.
So bare minimum disk space required for the installation to succeed should be clearly specified.

I experimented with various virtual disk image sizes:

• with 4 GiB image, Anaconda doesn't start the installation with lack of space error
• 7 GiB image: Anaconda installer didn't complain, installation started but didn't succeed
• 10 GiB passed

Ideally, Anaconda should not start the installation if it's known beforehand it won't succeed due to lack of space.
So that is the BUG of Anaconda, I assume.

Anyway, the 10 GiB could be mentioned as safe for installation of various SB versions.

[travier]

The same constraints as for the reset of Fedora apply: https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/

The minimum supported is 15GB, the recommended is 20GB.

[travier]

If you want to save on disk space, you can skip the Flatpak installation via a custom Kickstart or remove them after the installation to save space in the VM.

[bam80]

The minimum supported is 15GB, the recommended is 20GB.

15GB is not minimum supported, but recommended minimum instead:

The figures below are a recommended minimum for the default installation

These are different.

What I'm talking about in this issue is bare minimum needed to install the system (e.g. to know what image size to install should I create, in the first place).
This is not documented anywhere.

[bam80]

If you want to save on disk space, you can skip the Flatpak installation via a custom Kickstart

How do I do that, please?

[travier]

The minimum supported is 15GB, the recommended is 20GB.

15GB is not minimum supported, but recommended minimum instead:

The figures below are a recommended minimum for the default installation

These are different.

What I'm talking about in this issue is bare minimum needed to install the system (e.g. to know what image size to install should I create, in the first place). This is not documented anywhere.

Sure, it is semantically different, but in the end it does not matter. If you make an installation with less than that, it may work, it may not work, and it's likely not tested at all.

Any modern virtualisation tools should be able create disk images that are dynamically provisioned and only consume disk space as needed.

Feel free to make a PR to link to those requirements in the docs here.

---

If you want to save on disk space, you can skip the Flatpak installation via a custom Kickstart

How do I do that, please?

Adding:

%pre
# Skip Flatpak installation
rm -rf /flatpak/repo
%end

at the top of your kickstart should do it.

Example script and kickstart: https://gitlab.com/fedora/ostree/scripts

[bam80]

Sure, it is semantically different, but in the end it does not matter. If you make an installation with less than that, it may work, it may not work, and it's likely not tested at all.

Still, user might need to know how much space the installation is actually takes vs just "recommended minimum" required.
So both should be documented, IMO (and now we know the digits).

Adding:

%pre
# Skip Flatpak installation
rm -rf /flatpak/repo
%end

at the top of your kickstart should do it.

Thanks, should really be useful for VMs!