-
-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Incorrectly created complete/incomplete folders #256
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
We only create folders in /downloads |
@Roxedus Thanks for the prompt response. Are you suggesting that the |
That is a safe bet. |
This was referenced Dec 5, 2023
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Current Behavior
I have following setup.
/share
and a local folder to/incomplete
.settings.json
to/config
before lighting up the container with following key settings."download-dir": "/share/default"
"incomplete-dir": "/incomplete"
After lighting up the container, I saw
complete
andincomplete
folders created inside my file share. I searched the code base and found a hardcode here. Might be relevant.Expected Behavior
User settings of
incomplete
andcomplete
folders should be honored rather than making assumptions with hardcode. In my case, they should be/share/default
and/incomplete
, respectively.Steps To Reproduce
docker-compose.yml
, make following mountssome_path:/incomplete
some_other_path:/share
settings.json
to/config
before lighting up the container with following key settings"download-dir": "/share/default"
"incomplete-dir": "/incomplete"
sudo docker compose up -d
incomplete
andcomplete
folders created insidesome_other_path
.Environment
CPU architecture
arm64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: