Updated Troubleshooting (asciidoc)

Common-errors.asciidoc

@@ -0,0 +1,9 @@
+# I have an error with my filesystem permissions
+
+If you see a message such as the following:
+
+```
+Cannot start service sql: b"error while creating mount source path '/var/local/szurubooru/sql': mkdir /var/local/szurubooru: read-only file system"
+```
+
+then you should ensure that the mountpoint for the data directory ($MOUNT_DATA in .env) is owned by UID/GID 1000:1000, but you need to do this on the host machine, not inside the container (Example: `chmod -R 1000:1000 /var/local/szurubooru` if your mountpoint is `/var/local/szurubooru`)

Troubleshooting.asciidoc

@@ -1,19 +0,0 @@
-# Permissions error:
-
- ➜  szuru git:(master) docker-compose up -d
- Starting szuru_elasticsearch_1 ... 
- Starting szuru_sql_1           ... error
- Starting szuru_elasticsearch_1 ... done
- ERROR: for szuru_sql_1  Cannot start service sql: b"error while creating mount source path '/var/local/szurubooru/sql': mkdir /var/local/szurubooru: read-only file system"
- ERROR: for sql  Cannot start service sql: b"error while creating mount source path '/var/local/szurubooru/sql': mkdir /var/local/szurubooru: read-only file system"
- ERROR: Encountered errors while bringing up the project.
- ➜  szuru git:(master) 
-
-**chown -R 1000:1000 the mountpoint for the data directory ($MOUNT_DATA in .env), but you need to do this on the host machine, not inside the container**
-
-eg. chmod -R 1000:1000 /var/local/szurubooru
-
-# "Could not fetch basic configuration from server.":
-
-ElasticSearch is failing to initialise, ensure vm.max_map_count parameter for ElasticSearch is changed, https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html#_set_vm_max_map_count_to_at_least_262144[Click here for instructions]
-