On Sun, 08.11.15 13:17, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > > 1- SELinux is disabled as the host distro is difficult to setup with > it, so it is OK > 2- Running modprobe bridge nf_nat br_netfilter failed with message: , > error: exit status 1" > These modules are indeed loaded on host. How can I make the container > aware of it?
I am pretty sure all container managers disallow loading kernel modules from within the container, and I think that's a good choice that way. Note that "container" means you do shared-kernel virtualization: you only have one kernel, and hence there's only one kernel to load kernel modules into. Hence loading a kernel modules on the host is sufficient to make its functionality available to the kernel. Now, not all functionality the kernel provides is available in containers (in fact only a small part actually is), and the software you are using assumes it is however. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel