From 6ae32fe294b0fc12df3cb6c2f337c235f3b68669 Mon Sep 17 00:00:00 2001 From: cytopia Date: Thu, 26 Jul 2018 08:44:31 +0200 Subject: [PATCH] Fix #288 by documenting some edge cases --- docs/support/troubleshooting.rst | 37 ++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) diff --git a/docs/support/troubleshooting.rst b/docs/support/troubleshooting.rst index 93a0c331..bc028e47 100644 --- a/docs/support/troubleshooting.rst +++ b/docs/support/troubleshooting.rst @@ -40,6 +40,43 @@ updates to Docker itself. If those exist, try to revert them and see if that was I heard many bug stories from fellow Windows users so far. A good contact point for that is the Docker forum itself: https://forums.docker.com/c/docker-for-windows +A few general things you should always do before attempting to open up issues are: + +**1. Used default settings from env-example** + + Try using the exact settings from ``env-example`` as variables might have been updated in git. + + .. code-block:: bash + + # Ensure everything is stopped + host> cp env-example .env + +**2. Clean, updated and minimal start** + + .. code-block:: bash + + # Ensure everything is stopped + host> docker-compose stop + host> docker-compose kill + host> docker-compose rm -f + + # Ensure everything is updated + host> docker-compose pull + + # Start again + host> docker-compose up php httpd bind + +**3. Reset Docker credentials:** + + As it might sound strange, this fix might indeed solve a lot of problems on Windows. + Go to your Docker settings and reset your credentials. + +**4. Shared volumes:** + + Ensure all your Devilbox data (Devilbox directory and project directory) are within the volumes + that are shared by Docker. If not add those in the Docker settings. + + Address already in use ----------------------