Fix Docker volume mount docs

Callum027 · Callum027 · commit fe328aaa143c · 2023-02-11T20:40:51.000+13:00
diff --git a/README.md b/README.md
@@ -113,7 +113,7 @@ Once you have a valid configuration file, you can try Buildarr on your local mac
 The following command will mount the current folder into the Docker container so `buildarr.yml` can be read, and start Buildarr in daemon mode.
 
 ```bash
-$ docker run -d --name buildarr -v ./:/config -e PUID=$(id -u) -e PGID=$(id -g) callum027/buildarr:latest
+$ docker run -d --name buildarr -v $(pwd):/config -e PUID=$(id -u) -e PGID=$(id -g) callum027/buildarr:latest
 ```
 
 If installed using `pip`, simply run the `buildarr` CLI command.
@@ -196,7 +196,7 @@ Buildarr is still early in development, and even currently implemented features
 If you encounter an issue or error while using Buildarr, please do a Buildarr ad-hoc run with verbose log output by executing `buildarr run --log-level DEBUG` and making an issue on [our GitHub repository](https://github.com/buildarr/buildarr/issues/new) explaining the issue and attaching the output. (Please ensure that any API keys or other sensitive information are obfuscated before submitting.)
 
 ```bash
-$ docker run -d --name buildarr -v ./:/config -e PUID=$(id -u) -e PGID=$(id -g) callum027/buildarr:latest run --log-level DEBUG
+$ docker run -d --name buildarr -v $(pwd):/config -e PUID=$(id -u) -e PGID=$(id -g) callum027/buildarr:latest run --log-level DEBUG
 ```
 
 For developers looking to make a contribution to this project, thank you! Documentation of the internal APIs is still in the works, so for now, the best way to learn how Buildarr works is to clone the project and have a look at the comments and docstrings.
diff --git a/docs/index.md b/docs/index.md
@@ -111,7 +111,7 @@ Once you have a valid configuration file, you can try Buildarr on your local mac
 The following command will mount the current folder into the Docker container so `buildarr.yml` can be read, and start Buildarr in daemon mode.
 
 ```bash
-$ docker run -d --name buildarr -v ./:/config -e PUID=$(id -u) -e PGID=$(id -g) callum027/buildarr:latest
+$ docker run -d --name buildarr -v $(pwd):/config -e PUID=$(id -u) -e PGID=$(id -g) callum027/buildarr:latest
 ```
 
 If installed using `pip`, simply run the `buildarr` CLI command.
@@ -194,7 +194,7 @@ Buildarr is still early in development, and even currently implemented features
 If you encounter an issue or error while using Buildarr, please do a Buildarr ad-hoc run with verbose log output by executing `buildarr run --log-level DEBUG` and making an issue on [our GitHub repository](https://github.com/buildarr/buildarr/issues/new) explaining the issue and attaching the output. (Please ensure that any API keys or other sensitive information are obfuscated before submitting.)
 
 ```bash
-$ docker run -d --name buildarr -v ./:/config -e PUID=$(id -u) -e PGID=$(id -g) callum027/buildarr:latest run --log-level DEBUG
+$ docker run -d --name buildarr -v $(pwd):/config -e PUID=$(id -u) -e PGID=$(id -g) callum027/buildarr:latest run --log-level DEBUG
 ```
 
 For developers looking to make a contribution to this project, thank you! Documentation of the internal APIs is still in the works, so for now, the best way to learn how Buildarr works is to clone the project and have a look at the comments and docstrings.
