From 3346c6bc3803ee9961bf2d7113e843889dd3f399 Mon Sep 17 00:00:00 2001 From: Josh Curl Date: Thu, 1 Dec 2016 13:34:04 -0800 Subject: [PATCH] Document module loading --- .../os/configuration/loading-kernel-modules/index.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/os/configuration/loading-kernel-modules/index.md b/docs/os/configuration/loading-kernel-modules/index.md index 2fb44490..b44e7b67 100644 --- a/docs/os/configuration/loading-kernel-modules/index.md +++ b/docs/os/configuration/loading-kernel-modules/index.md @@ -7,6 +7,18 @@ layout: os-default ## Loading Kernel Modules --- +Kernel modules can be automatically loaded with the `rancher.modules` cloud-config field. + +```yaml +#cloud-config +rancher: + modules: [btrfs] +``` + +This functionality is also available via a kernel parameter. For example, the btrfs module could be automatically loaded with `rancher.modules=[btrfs]` as a kernel parameter. + +### Loading Kernel Modules via a System Service + Privileged containers can load kernel modules. In RancherOS, the kernel modules are in the standard `/lib/modules/$(uname -r)` folder. If you want to be able to run `modprobe` from a container, you will need to bind mount the `/lib/modules` into your container. ```yaml