Update FAQ.md

Updated: Path isn't valid
TRaSH 2020-07-28 20:23:36 +02:00
parent bd897f9a72
commit 1fadefd109

14
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) - 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 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* > *And yes this even works on a Synology*
> *if you don't know how you probably didn't read the [[Installation-Synology]]* > *if you don't know how you probably didn't read the [[Installation-Synology]]*
------ ------