Comment 22 for bug 1947601

Thank you very much, Dave, for taking the time to consider my input.

> I'm not convinced changing that to "sudo apt install docker.io
> linux-modules-extra-raspi" is such a burden?

For me no longer, since I know about it now. For all other ubuntu
users out there, who do not know about this workaround yet: yes, very
much so. The promise of apt is, that the user only has to know which
software they want to install, and apt will automatically install the
dependencies. This promise is broken here. Also consider the
users who will upgrade from 20.04 to 22.04 in half a year, and who
will also at first be surprised that their usual method of running
docker will no longer work.

Thanks for updating the release notes. Please note that there is a
typo that you may want to correct (rapsi -> raspi) in the workaround
command.

With regard to a possible fix:

I have checked which kernel modules are needed from the current
modules-extra package to run my docker projects: It really is only
veth, no other module is missing from the main modules package.

You say that rarely-used modules got transferred to the
modules-extra package. I would like to ask again that veth be
reconsidered as more-often-than-rarely used because it is essential
for docker, docker being quite popular on raspberry pi servers,
and because it is so small that it does not interfere with your
boot time acceleration goal.

Another possible fix would be fixing the dependencies. This is
more complicated than moving veth back to main modules, but I'm
sure it can be done in some way. I'm not an apt dependency expert,
but isn't it possible to have docker.io depend on a virtual package
veth, and then have different parts of the ARM kernel module
packages provide this veth module. I'm sure there is also a ton
of other possibilities, but all of them more complicated than
simply moving the module back.