Closed barukh27 closed 10 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
You can bind mount any path you like as long as it doesn't interfere with a path the container manages
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?
Is there an existing issue for this?
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
Container logs