#104 Workstation x86_64 live image is over size target
Closed: Fixed 3 months ago by catanzaro. Opened 3 months ago by chrismurphy.

https://bugzilla.redhat.com/show_bug.cgi?id=1751438

Summary of that bug and discussion at go/no-go meeting

Fedora-Workstation-Live-x86_64-31_Beta-1.1.iso has size 2047475712 bytes while max allowed size is 2000000000 bytes according to https://fedoraproject.org/wiki/Releases/31/ReleaseBlocking .

Release criterion makes this an automatic blocker for beta. However, it was reconsidered under the "Last minute blocker" policy to not be a beta blocker. As it stands, it will be a final blocker.

Discussed in blocker review/go+nogo meeting as the likely causes:
podman ~125MiB (newly added)
bcm283x-firmware (update grew ~11 MiB, +50%, overnight back in June)

More details (perhaps too many more) in this rawhide difference report from back when the image started to bust the limit:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/65Q4CM4EX5MXYYDD36TBCHGJACGA5BDT/

The Workstation working group either needs to increase the maximum size for this ISO, or we need to cut packages.

Is the 2GiB limit mostly about media availability? 8GB USB sticks ~$3.
Reasons for NOT bumping the maximum size to 4GB/3.73GiB?


Why is the podman package so fat?

podman ~52 M
Dependencies:
containernetworking-plugins ~ 71 M

from rpm -qi containernetworking-plugins
Description :
The CNI (Container Network Interface) project consists of a specification
and libraries for writing plugins to configure network interfaces in Linux
containers, along with a number of supported plugins. CNI concerns itself
only with network connectivity of containers and removing allocated resources
when the container is deleted.

I'm not worried about podman; that belongs.

Can we see an analysis of what packages are using the most space on the live image? I remember an issue with Noto fonts a couple years ago, for example; I'm not sure if that was ever satisfactorily resolved or not.

Is the 2GiB limit mostly about media availability? 8GB USB sticks ~$3.
Reasons for NOT bumping the maximum size to 4GB/3.73GiB?

It's not just media availability. Potential users with slow internet connections who want to try Fedora might prefer other distros if our media size increases beyond reason.

I think we should be OK with requiring a 4 GB USB stick in 2019, but a much smaller max size bump seems warranted so that we can keep a handle on media size bloat. Say 2.2 GB.

Can we see an analysis of what packages are using the most space on the live image? I remember an issue with Noto fonts a couple years ago, for example; I'm not sure if that was ever satisfactorily resolved or not.

That was #46

I'm not worried about podman; that belongs.

Why does podman belong? I can't seem to find a ticket about adding it for Workstation...

Recent image sizes

1931476992      Fedora-Workstation-Live-x86_64-29-1.2.iso
1934753792      Fedora-Workstation-Live-x86_64-30-1.2.iso
2047475712      Fedora-Workstation-Live-x86_64-31_Beta-1.1.iso

That means F31b is ~107MiB bigger than F30.

F30 Workstation Live RPMs size sort
https://paste.fedoraproject.org/paste/cco9PGTzrhxyKLrtHuZSvQ

F31 Workstation Live RPMs size sort
https://paste.fedoraproject.org/paste/rRgBQ3OzALGPsZhhphXDvg

I'm tentatively expecting image size goes up ~5% for Fedora 32 if the image moves to plain squashfs + ZSTD compression. Bringing ISO size to 2.15GB/2.00GiB
https://pagure.io/releng/issue/8646
https://pagure.io/releng/issue/8581

That was really helpful, thanks.

The packages look sane to me. I don't see any problem with having podman. We just don't want to accidentally miss something huge being pulled in by mistake.

I'm not worried about podman; that belongs.

Why does podman belong? I can't seem to find a ticket about adding it for Workstation...

https://pagure.io/fedora-workstation/issue/49

You'd have to dig up the meeting minutes for the full discussion, but the gist of it (as far as I'm concerned), is that the primary target of Fedora Workstation is developers and containers are a basic tool for many contemporary developers.

We also want to default to consistency between Silverblue and traditional Fedora Workstation unless there is a strong reason to deviate, and you can't get much development at all done on Silverblue without podman.

Well it's clear we have to either (a) increase the image size, or (b) not add podman. And podman is important for our strategy.

It's clear we don't have support for raising the image size to 3 GB. How about my proposal of 2.2 GB?

@catanzaro Sure, I'm okay with 2.2GB. I'd like to see if we can get back under the 2GB barrier, but if not, that's an acceptable compromise.

Some quick observations:

F30 -> F31

linux-firmware +21Mb
google-noto-sans-cjk-ttc-fonts +10Mb
iwl7260-firmware +12Mb
kernel-core +6Mb

Does anyone know why Firebird has been added to F31 Workstation? It's now installed by default, it wasn't for F30. Is it intentional? I'm not seeing anything else depending on it.

https://paste.fedoraproject.org/paste/twhmDV6KCJksJ8effBTGOQ

@chrismurphy it seems to be a dependency of libreoffice-core.

We are now under size target thanks to the removal of the serif CJK font.

@petersen says it is nice to have installed, but the cost is very heavy (over 100 MB).

So we have no need to raise the size target for now. Next time we exceed the size target, we'll analyze the situation and decide how to react (whether or not to raise the size target).

Closing.

Metadata Update from @catanzaro:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 months ago

Metadata Update from @catanzaro:
- Issue untagged with: meeting

3 months ago

Login to comment on this ticket.

Metadata