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

qBittorrent volume not properly mapping? #368

Open
GitHubQueenn opened this issue Jan 25, 2025 · 11 comments
Open

qBittorrent volume not properly mapping? #368

GitHubQueenn opened this issue Jan 25, 2025 · 11 comments
Labels

Comments

@GitHubQueenn
Copy link

GitHubQueenn commented Jan 25, 2025

Hi. So, I have a config folder mapped and a downloads folder mapped, but for some reason when I try to map an "incomplete" folder (while a torrent is downloading or fails or whatever), Docker is creating an "incomplete" folder when I start the container instead of mounting to the "Incomplete" (capitalized) folder that is already there. In qBitt settings, my incomplete path is also properly set to the "Incomplete" folder I made.

My map looks like:

/media/folder1/folder2/Incomplete:/downloads/incomplete

Am I doing something wrong? Any other time I've mapped anything else to a folder I've already made an properly capitalized, I never had this issue. Native machine is Ubuntu. This worked fine on native so I'm not sure why Docker is doing this.

@LinuxServer-CI LinuxServer-CI moved this from Issues to Insufficient Info in Issue & PR Tracker Jan 25, 2025
Copy link

A human has marked this issue as invalid, this likely happened because the issue template was not used in the creation of the issue.

@GitHubQueenn
Copy link
Author

@j0nnymoe Instead of just invalidating the question, can you answer it? I'm sure it's not a hard one for you, but I am new to this.

@Roxedus
Copy link
Member

Roxedus commented Jan 25, 2025

The issue section is for issues, not support request. The issue templates also reflects that, support goes on our forum or discord.

@j0nnymoe
Copy link
Member

@j0nnymoe Instead of just invalidating the question, can you answer it? I'm sure it's not a hard one for you, but I am new to this.

Perhaps answer the questions that are in the template on the first place as well otherwise I'm just going to repeat the questions that you've already ignored.

@GitHubQueenn
Copy link
Author

GitHubQueenn commented Jan 25, 2025

Perhaps answer the questions that are in the template on the first place as well otherwise I'm just going to repeat the questions that you've already ignored.

I gave the only relevant info you'd need and the OS I'm on. Just seeing if there's anything wrong with how I have that mapped.

@j0nnymoe
Copy link
Member

If we're setting it in a template, we think it's relevant.

@GitHubQueenn
Copy link
Author

If we're setting it in a template, we think it's relevant.

Is the below properly formatted for mapping?
/media/folder1/folder2/Incomplete:/downloads/incomplete

I just need a "yes" or "no." Because if so, it's weird that the container is making the lowercase "incomplete" folder when I specified one already on the host.

@j0nnymoe
Copy link
Member

Looks fine other than Incomplete is a different folder to incomplete on Linux. Saw something similar happening to a QNAP user.

@GitHubQueenn
Copy link
Author

GitHubQueenn commented Jan 25, 2025

Looks fine other than Incomplete is a different folder to incomplete on Linux. Saw something similar happening to a QNAP user.

Interesting. Yeah, in my example in my last reply, that's how I have it mapped. With the proper "Incomplete" on my local host. Do I also need to change the lowercase Docker "incomplete" to uppercase to match? I thought that would break it or that I should leave it alone since that's on Docker's side.

In my qBitt settings, I also have it properly set to the uppercase "Incomplete" folder. Unless qBitt doesn't even have a "/downloads/incomplete" path to begin with in the program itself...

@j0nnymoe
Copy link
Member

Wouldn't know, never been in this situation. I would just have lowercase for all folders.

@GitHubQueenn
Copy link
Author

GitHubQueenn commented Jan 25, 2025

Wouldn't know, never been in this situation. I would just have lowercase for all folders.

Ah, ok. Yeah, I like to be grammatically proper and start words with capital letters with my folders, so maybe for this one time I will use lowercase. Weird since it works with other containers I've done the lowercase/uppercase thing with. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Insufficient Info
Development

No branches or pull requests

3 participants