What happens when a container-init calls clone() with the CLONE_PARENT flag set ? Since CLONE_PARENT can be used to create a sibling, I'd think that this will create a sibling, in particular, a new task in the same container whose parent is the parent of the container. From a quick look in the code I can't see why this would be impossible. Is this so ? Is this the desired behavior ? Oren. _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
