Debian unable to create initrd due out-of-sync repository about mkosi HOT 2 CLOSED

@lunix33 The provided config does not reproduce the issue.

I'm not sure if I'm mishandling the cache or doing something improperly. I've been using mkosi-chroot apt-get ... to install my packages in the chroot instead of using the helper in /scripts, since I need my custom repositories and keys (which gets added and dearmored during the prepare (final) script) to be available in the final image, and from what I understand putting them in /etc/apt/... (not within the chroot), which the script seems to be using, would not make them available in the final image. Should I create the files in both? Have I missed somthing in the documentation when it comes to handling cache and package install?

You need to add put repositories in a mkosi.skeleton/ tree. Specifically in mkosi.skeleton/etc/apt/sources.list.d. Then they will be taken into account by mkosi and will be available in the final image.

I'm guessing that whatever you're doing in your scripts is getting rid of the repository metadata which we need to build the initrd later on.

from mkosi.

Thanks for the information you gave me, I'll take your recommandation into consideration.

When it comes to the actual issue at hand, after some more test I was able to get things working as expected after reading about that the script actions could affect the initrd generation. I started the project with a prototype on v21, and seems like some of the operations that were working in v21 stopped working with v22 (like deleting the package list within the chroot, though some of the configuration changed since then, and scripts were rewritten, so that might also be it). So removing those operations seem to fix my issue, when it comes to building the default initramfs. I've added a RemoveFiles configuration to delete the content of /var/lib/apt/lists within the final rootfs.

from mkosi.