Skip to content
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] Incomplete folder #260

Closed
1 task done
barukh27 opened this issue Oct 24, 2023 · 3 comments
Closed
1 task done

[BUG] Incomplete folder #260

barukh27 opened this issue Oct 24, 2023 · 3 comments

Comments

@barukh27
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

When you download a file a folder "incomplete" is created. The same happens with a folder "complete".

Expected Behavior

It would be better to have a volume (/hostpathtoincomplete) to bind the folder (/incomplete).

Steps To Reproduce

Volumes created as docker-compose template.

Environment

No response

CPU architecture

arm64

Docker creation

volumes:
      - /path/to/data:/config
      - /path/to/downloads:/downloads
      - /path/to/watch/folder:/watch

Container logs

-
@github-actions
Copy link

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@aptalca
Copy link
Member

aptalca commented Oct 24, 2023

You can bind mount any path you like as long as it doesn't interfere with a path the container manages

@aptalca aptalca closed this as completed Oct 24, 2023
@barukh27
Copy link
Author

You can bind mount any path you like as long as it doesn't interfere with a path the container manages

Thank you for your reply.

So, if I bind /mnt/incompletes to /incomple it should work.

I have another question, the folder "complete" and "downloads" is the same. If not, how is it that the folder "complete" is created?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants