Avoid using valid path for illustrative purpose

Otherwise docker will really create this example path on host machine
which is bad.
This commit is contained in:
Chocobo1 2022-05-05 11:48:35 +08:00
parent 4894578b72
commit bc54860ad6
No known key found for this signature in database
GPG key ID: 210D9C873253A68C

View file

@ -42,8 +42,8 @@ docker build \
-p "$QBT_WEBUI_PORT":"$QBT_WEBUI_PORT" \ -p "$QBT_WEBUI_PORT":"$QBT_WEBUI_PORT" \
-p 6881:6881/tcp \ -p 6881:6881/tcp \
-p 6881:6881/udp \ -p 6881:6881/udp \
-v /your_path/config:/config \ -v <your_path>/config:/config \
-v /your_path/downloads:/downloads \ -v <your_path>/downloads:/downloads \
qbittorrent-nox:"$QBT_VERSION" qbittorrent-nox:"$QBT_VERSION"
``` ```
Then you can login at: `http://127.0.0.1:8080` Then you can login at: `http://127.0.0.1:8080`
@ -67,5 +67,5 @@ docker build \
### Volumes ### Volumes
There are some paths involved: There are some paths involved:
* `/your_path/config` on your host machine will contain qBittorrent configurations * `<your_path>/config` on your host machine will contain qBittorrent configurations
* `/your_path/downloads` on your host machine will contain the files downloaded by qBittorrent * `<your_path>/downloads` on your host machine will contain the files downloaded by qBittorrent