copymods results in new mods installed by apt disappearing after reboot
Bug #1989995 reported by
Jason
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloud-initramfs-tools |
New
|
Undecided
|
Unassigned | ||
Bug Description
If copymods results in a booted state where /lib/modules is a tmpfs, then a package like ...modules-extra is installed later, apt installs them into a tmpfs and not the disk and they disappear after reboot. It could be that ...modules-extra should be adding hooks to get these modules added to the initramfs, but are all modules supposed to be there?
If not, I don't even understand how this is supposed to work after the initial boot.
It currently does not.
Revision history for this message
| Jason (jasmas) wrote | #1 |
To post a comment you must log in.
I am seeing this behavior on a raspberry pi. I am using docker which now requires several modules from ...modules-extra, but having a problem where the oob behavior is the system works fine until at some point modules disappear and the docker daemon can't boot on reboot.
Extensively searching the internet you can find this issue showing up a lot where extra kernel modules get installed.
I have traced the problem I am having back to the copymods package which it seems results in a tmpfs holding all modules.
It doesn't seem like apt always knows this.. Or at least there are some states where apt installs additional modules which somehow don't make it to the tmpfs modules folder on reboot.