You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docker run -d -p 9999:9999 -v /media/Download:/download
The specified download directory for docker startup is invalid
Version: v1.3.5, the previous version is normal
After the specified directory is started, it is still downloaded to the /var/lib/docker/overlay2/b8d486770c2c1b623a141cd7f94f776bd355f793652e1f3bffaf1ba1652fcdb3/merged/root/Downloads directory
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
docker启动,指定下载目录无效
docker启动,指定下载目录无效 || docker starts, the specified download directory is invalid
Jul 19, 2023
docker run -d -p 9999:9999 -v /media/Download:/root/Downloads
当然我的文档可能也有点误导性,等会我更新下docker命令。
The container is downloaded to the /root/Downloads directory by default. The directory you mount is /download. You need to modify the download directory in the downloader:
Or re-run a new container with this command:
docker run -d -p 9999:9999 -v /media/Download:/root/Downloads
Of course, my documentation may be a bit misleading, I will update the docker command later.
monkeyWie
changed the title
docker启动,指定下载目录无效 || docker starts, the specified download directory is invalid
docker starts, the specified download directory is invalid
Jul 19, 2023
docker run -d -p 9999:9999 -v /media/Download:/download
docker 启动指定下载目录无效
版本: v1.3.5, 上一个版本正常
指定目录启动后,依旧下载到/var/lib/docker/overlay2/b8d486770c2c1b623a141cd7f94f776bd355f793652e1f3bffaf1ba1652fcdb3/merged/root/Downloads目录下
docker run -d -p 9999:9999 -v /media/Download:/download
The specified download directory for docker startup is invalid
Version: v1.3.5, the previous version is normal
After the specified directory is started, it is still downloaded to the /var/lib/docker/overlay2/b8d486770c2c1b623a141cd7f94f776bd355f793652e1f3bffaf1ba1652fcdb3/merged/root/Downloads directory
The text was updated successfully, but these errors were encountered: