From 088608d160a39f6dc64ba305c473dd3390140ac7 Mon Sep 17 00:00:00 2001 From: Jose Diaz-Gonzalez Date: Sat, 19 May 2018 14:13:55 -0400 Subject: [PATCH] docs: add warning to running on external volumes --- docs/community/tutorials/run-on-external-volume.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/community/tutorials/run-on-external-volume.md b/docs/community/tutorials/run-on-external-volume.md index 2476f0505..b212495fb 100644 --- a/docs/community/tutorials/run-on-external-volume.md +++ b/docs/community/tutorials/run-on-external-volume.md @@ -3,7 +3,10 @@ In order to leverage cloud-provider facilities like _attachable volumes_, (_a.k.a. block storage_) the following is an easy tutorial to achieve Dokku runs on them. +> Warning: If the block storage is not available and attached on boot it is possible that containers will not correctly start. Please keep this in mind when considering moving Dokku and/or Docker to network attached storage. + ## Tutorial + The following is intended to be executed on the dokku host machine as `root`. Say, _for instance_, that our volume is mapped into the systems as `/dev/vdb1`.