Quoting Michael H. Warfield (m...@wittsend.com): > My second takeaway from the Linux Plumbers conference was to do an > automatic heuristic determination when we should enable autodev > (mounting of something on /dev/ in the container at startup for things > like systemd). If autodev is not enabled when it is required (systemd) > the container can cause the host to hang or behave indeterminently due > to devtmpfs being mounted in both the host and the container.
I don't understand... shouldn't it suffice for the fedora (and other systemd-based) template to always set autodev to 1? Leaving the decision entirely up to the template also should simplify doing the /dev/$container/ bind-mount into $container/dev like you were wanting to do. The template can "just do it" without having to worry about being second-guessed by lxc itself. There are plenty of ways for a wrong or malicious template to hose the system - this is just one more. Hardcoding a "fix" for this in lxc itself will, I fear, only make things more complicated if/when there is a change to devtmpfs behavior, i.e. if it were to start supporting newinstance mounts. -serge ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk _______________________________________________ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
