After digging a while I found that this issue is produced by the installation of apparmor-profiles package. The installation of this package causes a restart of the apparmor service which somehow leaves something opened (I couldn't actually figure out what) related to the chrooted /sys. I am passing this issue to apparmor maintainers, I hope they can debug what is actually happening here when installing apparmor packages in a chrooted env.