From 1fadefd109c0245966857309a0d401e74dc23302 Mon Sep 17 00:00:00 2001 From: TRaSH Date: Tue, 28 Jul 2020 20:23:36 +0200 Subject: [PATCH] Update FAQ.md Updated: Path isn't valid --- FAQ.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/FAQ.md b/FAQ.md index 04e87a0..37c99b2 100644 --- a/FAQ.md +++ b/FAQ.md @@ -54,20 +54,20 @@ This can be for various reasons we've collected the the most common ones dependi - In worse case scenario you need to make use of [Paths Mapping](https://github.com/morpheus65535/bazarr/wiki/Settings#path-mappings) - +#### NOTE: > *If you're using docker and get this warning and need help with it provide us with the docker compose or docker build command of Bazarr and Sonarr/Radarr !!!* > -> *If you're using a system with a GUI(Synology, unRAID, OMV, etc.) to configure docker use one of the following from terminal(puTTy) to get the docker compose or docker build command.*` +> *If you're using a system with a GUI(Synology, unRAID, OMV, etc.) to configure docker use one of the following from terminal(puTTy) to get the docker compose or docker build command.*` > -> `docker run --rm -v /var/run/docker.sock:/var/run/docker.sock assaflavie/runlike CONTAINER_NAME` +> `docker run --rm -v /var/run/docker.sock:/var/run/docker.sock assaflavie/runlike CONTAINER_NAME` > -> *or* +> *or* > -> `docker run --rm -v /var/run/docker.sock:/var/run/docker.sock red5d/docker-autocompose CONTAINER_NAME` +> `docker run --rm -v /var/run/docker.sock:/var/run/docker.sock red5d/docker-autocompose CONTAINER_NAME` > -> *And yes this even works on a Synology* -> *if you don't know how you probably didn't read the [[Installation-Synology]]* +> *And yes this even works on a Synology* +> *if you don't know how you probably didn't read the [[Installation-Synology]]* ------