2018-04-03 00:06:12 +00:00
|
|
|
.. _troubleshooting:
|
|
|
|
|
2018-04-02 13:47:41 +00:00
|
|
|
***************
|
|
|
|
Troubleshooting
|
|
|
|
***************
|
|
|
|
|
|
|
|
This section will contain common problems and how to resolve them.
|
|
|
|
It will grow over time once there are more issues reported.
|
|
|
|
|
2018-04-03 00:06:12 +00:00
|
|
|
.. seealso:: :ref:`faq`
|
|
|
|
|
2018-04-02 13:47:41 +00:00
|
|
|
|
|
|
|
**Table of Contents**
|
|
|
|
|
|
|
|
.. contents:: :local:
|
|
|
|
|
|
|
|
|
|
|
|
Invalid bind mount spec
|
|
|
|
-----------------------
|
|
|
|
|
|
|
|
This error might occure after changing the path of MySQL, PgSQL, Mongo or any other data directory.
|
|
|
|
|
|
|
|
When you change any paths inside ``.env`` that affect Docker mountpoints, the container need to be
|
|
|
|
removed and re-created during the next startup.
|
|
|
|
Removing the container is sufficient as they will always be created during run if they don't exist.
|
|
|
|
|
|
|
|
In order to remove the container do the following:
|
|
|
|
|
|
|
|
|
|
|
|
.. code-block:: bash
|
|
|
|
|
|
|
|
host> cd path/to/devilbox
|
|
|
|
host> docker-compose stop
|
|
|
|
|
|
|
|
# Remove the stopped container (IMPORTANT!)
|
|
|
|
# After the removal it will be re-created during next run
|
|
|
|
host> docker-compose rm -f
|
2018-04-02 14:35:27 +00:00
|
|
|
|
|
|
|
.. seealso:: :ref:`remove_stopped_container`
|