Am 08.11.2015 um 15:41 schrieb arnaud gaboury:
On Sun, Nov 8, 2015 at 2:57 PM Richard Weinberger <richard.weinber...@gmail.com <mailto:richard.weinber...@gmail.com>> wrote: On Sun, Nov 8, 2015 at 1:17 PM, arnaud gaboury <arnaud.gabo...@gmail.com <mailto:arnaud.gabo...@gmail.com>> wrote: > I am trying to understand how kernel modules are "passed" to nspawn container. A container must not load any module as the kernel is a shared resource. So, why my container, and especially docker.service, is not aware of the loaded modules from the host?
because he has no business to do so? kernel modules ahre *hardware drivers* there is no classical hardware in a containerif you need that for whatever reason than don't use containers but full virtualization
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
