fwupd it happens pulls in not only ModemManager but also udisks2, so there are two daemons running in every container as a result of fwupd's presence.
Having discussed with the CPC team, it doesn't make sense to include fwupd in any cloud or container images, unless there's a particular partner image that's used on baremetal and exposes devices for firmware updates.
So since fwupd is only a recommends of ubuntu-server, we can and should just remove this package during the image build.
Leaving the ubuntu-meta task open because we probably do want to refactor the seeds so that such removals are not necessary during the image build.
fwupd it happens pulls in not only ModemManager but also udisks2, so there are two daemons running in every container as a result of fwupd's presence.
Having discussed with the CPC team, it doesn't make sense to include fwupd in any cloud or container images, unless there's a particular partner image that's used on baremetal and exposes devices for firmware updates.
So since fwupd is only a recommends of ubuntu-server, we can and should just remove this package during the image build.
Leaving the ubuntu-meta task open because we probably do want to refactor the seeds so that such removals are not necessary during the image build.