search

linuxserver / docker-radarr

GNU General Public License v3.0
640 stars 103 forks source link

Remove Poor Docker Path Suggestions #138

Closed bakerboy448 closed 3 years ago

bakerboy448 commented 3 years ago

linuxserver.io

Desired Behavior

Proper docker path suggestions like here and here in the suggested compose or no suggestions at all

Current Behavior

Current behavior results in users having frequent issues due to improperly configured docker mounts. Also results in users using 2x the space for seeding torrents and extra wear and tear on the hard drives

Alternatives Considered

Continue to frustrate users, application support staff, and LSIO support staff and confuse users as they will have a health check until this is resolved.

github-actions[bot] commented 3 years ago

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

aptalca commented 3 years ago

Please stop opening countless issues. Numerous duplicate issues have been opened in the past on this.

bakerboy448 commented 3 years ago

Then why not make the change(s) then. Why continue to cause health checks in applications, intentionally cause excessive wear and tear on hard drives, and waste everyone’s time fixing the issues caused by the bad suggestions?

Correcting the suggested paths will save hundreds of hours of time in the world.

edit: I also do not see a single issue here specifically referencing this type of request.

I do however see numerous issues opened that are a direct result of these paths.

aptalca commented 3 years ago

Have you considered the possibility that we simply don't agree with you and have different goals and priorities than you?

bakerboy448 commented 3 years ago

And what goals are those?

Assuming multiple mounts is part of those goals. Then I ask why do you have goals that are detrimental to the user and causes excessive wear and tear on their hardware do not seem like good goals to me.

Still waiting for those duplicate issues you claim to exist.

aptalca commented 3 years ago

The goal is to come up with a recommended sample config that works for most if not all users out of the box, and simply implemented.

What you're suggesting is to recommend a config that works really well for a small percentage of users who actually need it, but it's difficult to implement for most users and causes more confusion.

With that said, I'll be blunt. You're coming off as a little too aggressive and accusatory. If you don't tone it down, I'll bow out of the convo, fyi.

bakerboy448 commented 3 years ago

We can switch over to discord for some more sanity/ease of comm; for posterity image

The goal is to come up with a recommended sample config that works for most if not all users out of the box, and simply implemented.

If use of the paths causes an error within the app and constant user support issues even if there is no error. I would say that is neither working nor simple.

What you're suggesting is to recommend a config that works really well for a small percentage of users who actually need it, but it's difficult to implement for most users and causes more confusion.

I'm suggesting to either make good suggestions or make no suggestions at all. Either one resolves the inherent issue at hand.

This is rather simple and easy to implement...well maybe not for users currently using the poorly planned 'suggested' paths. Those folks seem to get confused with a simpler setup.

image

bakerboy448 commented 3 years ago

@aptalca I think we got off on the wrong foot and I came in swinging the bat a bit too aggressively along with a shotgun of bats. For that, I apologize.

Some alt solutions briefly discussed on discord that would help overall without needing to redo the paths

I think these changes would significantly cut down on support on the app side, unraid side, and LSIO side. Users commonly have the false believe that (in this case) the application requires /movies and /downloads when that is not the case.

Of course ideally users would actually read the docs, but that never happens. One theory is users just use their docker GUI to find and pull the containers, never going near any documentation.

github-actions[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.