If my understanding is correctl, to stop systemd trying to launch udev and generally make a mess of everything inside a container, you need to remove the mknod capability from the container. But what if I want (need) to be able to use mknod inside a container, how can I do that with a systemd container?
I have this container that is a builder of system images for other nodes (containers and/or metal boxes). In order to correctly do this it needs to execute mknod inside the image as it builds it. (note, device nodes created doesn't need to be usable in the context of the image being built - the builder just needs to be able to create it). I've been doing this for ages under sysvinit and it's been fine. I have just migrated this builder container to systemd and hit this problem... Is there another way to keep systemd in line other than removing the mknod capability ? Thanks, John ------------------------------------------------------------------------------ Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
