From 51d56a7fd52ca8ec8e3d30354b7ea276c801da0c Mon Sep 17 00:00:00 2001 From: Alain Domissy Date: Tue, 25 Oct 2016 08:06:41 -0700 Subject: [PATCH] ENABLE OVERLAY default is no typo ? in version 2.2 , ENABLE OVERLAY default seems to be no --- pages/docs/admin-docs/advanced-config.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/docs/admin-docs/advanced-config.md b/pages/docs/admin-docs/advanced-config.md index e05014c..8d0a013 100644 --- a/pages/docs/admin-docs/advanced-config.md +++ b/pages/docs/admin-docs/advanced-config.md @@ -25,7 +25,7 @@ While the PID namespace is a *neat* feature, it does not have much practical usa Even if the PID namespace is enabled by the system administrator here, it is not implemented by default when running containers. The user will have to specify they wish to implement un-sharing of the PID namespace as it must fork a child process. -### ENABLE OVERLAY (boolean, default='yes') +### ENABLE OVERLAY (boolean, default='no') The overlay file system creates a writable substrate to create bind points if necessary. This feature is very useful when implementing bind points within containers where the bind point may not already exist so it helps with portability of containers. Enabling this option has been known to cause some kernels to panic as this feature maybe present within a kernel, but has not proved to be stable as of the time of this writing (e.g. the Red Hat 7.2 kernel). ### CONFIG PASSWD,GROUP,RESOLV_CONF (boolean, default='yes')