From 93456ab28c53916676eede9a348274fd527a36a9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Felix=20Geisendo=CC=88rfer?= Date: Wed, 16 Dec 2015 13:20:25 +0000 Subject: [PATCH] docs: warn about virtualbox sendfile issue MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This is a common issue new users may experience, so it seems worth warning about. See https://github.com/docker/docker/issues/18666 Signed-off-by: Felix Geisendörfer --- docs/drivers/virtualbox.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/drivers/virtualbox.md b/docs/drivers/virtualbox.md index 64992d86f2..471e19f41b 100644 --- a/docs/drivers/virtualbox.md +++ b/docs/drivers/virtualbox.md @@ -78,3 +78,13 @@ Environment variables and default values: | `--virtualbox-hostonly-nicpromisc` | `VIRTUALBOX_HOSTONLY_NIC_PROMISC` | `deny` | | `--virtualbox-no-share` | `VIRTUALBOX_NO_SHARE` | `false` | | `--virtualbox-dns-proxy` | `VIRTUALBOX_DNS_PROXY` | `false` | + +## Known Issues + +Vboxfs suffers from a [longstanding bug](https://www.virtualbox.org/ticket/9069) +causing [sendfile(2)](http://linux.die.net/man/2/sendfile) to serve cached file +contents. + +This will often cause problems when using a web server such as nginx to serve +static files from a shared volume. For development environments, a good +workaround is to disable sendfile in your server configuration.