With livecd-tools-16.5-1.fc16.x86_64 I have started getting errors like umount: /var/tmp/imgcreate-neqeMN/install_root/sys/fs/selinux/load: not found after the livecd-creator image building has completed. The image works fine. I haven't been able to figure out why - the code looks correct. My best bet would be if /sys/fs/selinux has been (lazily) unmounted before it tries to umount the fake load mount.
I also the same problem on the latest live-tools source codes. http://git.fedorahosted.org/git/?p=livecd;a=summary In the process of mount/umount, both have this error. mount: install_root/sys/fs/selinux/load: not exist umount: install_root/sys/fs/selinux/load: not found
Do you have selinux enabled on the build host? Are you building an image with selinux enabled or disabled? It is probably some combination of those two settings.
On the build host I have SE enabled but permissive (otherwise I get too many errors and don't trust the image). I am building an image that has selinux --enforcing.
Does /sys/fs/selinux exist on the buildhost? And is there a line in the logs about skipping it? I suspect this is caused by a host/target mismatch of the selinux mountpoint. I'm seeing it on my F15 system with selinux disabled on the host.
I don't have the machine right and can't give the full answer now, but: SELinux do in general work fine on the host machine, so I assume /sys/fs/selinux is correctly mounted. Which logs should mention any skipping and exactly how should the line look like? (I haven't noticed it and I assume I would have noticed it if it was a place I would look ... but that doesn't prove anything.) I do however run updates-testing on the build host and only updates on the image I compose. The policy version might thus be "slightly" different. Do you expect that is enough to cause this?
It looks like this when I run with -v -d --logfile=build.log Extending sparse file /var/tmp/imgcreate-VXruDL/tmp-aABXm_/ext3fs.img to 1073741824 Mounting /dev/loop3 at /var/tmp/imgcreate-VXruDL/install_root Skipping (/sys/fs/selinux,/sys/fs/selinux) because source doesn't exist. Retrieving http://mirrors.kernel.org/fedora/development/rawhide/x86_64/os/repodata/repomd.xml ...OK A policy difference shouldn't be enough, it is the mountpoint that's having problems.
livecd-tools-16.11-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/livecd-tools-16.11-1.fc16
livecd-tools-16.11-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.