@Serge, thanks for your comments.
I have experimented a little more. And I found that --path is indead at the very least misleading: If I don't use --path, then the config (snippet) given to lxc-create by "-f" is merged with the config that the template creates. If i do use paht, then the -f file is put under /var/lib/lxc while the template creates is stored under the --path. So at least this is bad and confusing. I also came up with the idea of linking or bind-mounting /var/lib/lxc to some other place. It seems safer ... :-) As for plymouth: I still have to experiment whether the behaviour is different when not using --path. But one of the main purposes for me to use is to get network virtualization, so it is not an option to _not_ configure network for my containers. :-) I usually use veth and one of the bridge devices created by libvirt. Cheers - Michael -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925513 Title: plymouth should not run in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
