Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Files added by docker are not deletable/writable through share

Featured Replies

I've installed a docker with Transmission. Once its downloaded a file, it'll put the file in the `download` share I've created. In the config for the download share, I've set security to "Public". I'm accessing the share as a normal user. I can write to, read from and delete from the share perfectly happily - so, security seems not to be in the way of things.

 

However, when I try to delete a downloaded file (again, downloaded by Transmission in a docker, and put in the download share automatically) I get "access denied". It appears I can read such files perfectly fine, but they'll have to remain there forever, because I can't delete them. Also, I can't put any new files in there either, which means the directory isn't writable. However, outside the download directory, I can read and write and delete as much as I want without error.

 

When I set the share permissions to "private" and give myself read/write permissions, the problem remains.

 

So, how do I allow write/delete permissions on a *folder* in a share?

 

I'm running unRAID 6.2.4 and accessing share by Windows 10.

There's probably a setting within transmission's GUI to set the permissions.  Use 0777 for them.

  • Author

Unfortunately, no there isn't... Any other ideas?

 

Also, would this be specific to Transmission or is this a common problem when using Docker images? (this is my first, ever)

Unfortunately, no there isn't... Any other ideas?

 

Also, would this be specific to Transmission or is this a common problem when using Docker images? (this is my first, ever)

Google

unraid transmission umask json

  • Author

I'm not sure what it is you're trying to get me to do. I know google, but cant you post a url to a guide that I'm supposed to find?

 

Please keep in mind my novice-ness with unRAID.

I'm not sure what it is you're trying to get me to do. I know google, but cant you post a url to a guide that I'm supposed to find?

 

Please keep in mind my novice-ness with unRAID.

Click on the first link of the search results. It outlines the issue and the solution.
  • Author

Ok, I get it. You're not that motivated to help me. Because that remark is much harder to type than copypasting the right url: https://lime-technology.com/forum/index.php?topic=40300.0

 

It's even on this very forum.

 

BUT, we're not there yet. It says I should edit `appdata/Transmission/settings.json`, which is not readable. Probably because of the very same problem.

 

So I stumbled upon this thing in Tools: http://unraid/Tools/DockerSafeNewPerms

And that appears to have fixed it.

 

I'm not sure where this tool came from, because I'm positive it wasn't there when I first installed unRAID. Maybe by some kind of magic, or maybe it's because of something else I installed, my novice-ness doesn't tell me why. But it's there. Hopefully it's also there for the next person with this problem.

Problem is, you've not told us what version of transmission you've installed.  The docker containers are not all made equal.  Link in my sig outlines how to post more info about docker, and it helps if you post in the support thread for the container you're using, because those are the ones we monitor.

Ok, I get it. You're not that motivated to help me. Because that remark is much harder to type than copypasting the right url: https://lime-technology.com/forum/index.php?topic=40300.0

 

It's even on this very forum.

 

BUT, we're not there yet. It says I should edit `appdata/Transmission/settings.json`, which is not readable. Probably because of the very same problem.

 

So I stumbled upon this thing in Tools: http://unraid/Tools/DockerSafeNewPerms

And that appears to have fixed it.

 

I'm not sure where this tool came from, because I'm positive it wasn't there when I first installed unRAID. Maybe by some kind of magic, or maybe it's because of something else I installed, my novice-ness doesn't tell me why. But it's there. Hopefully it's also there for the next person with this problem.

DockerSafeNewPerms will fix permissions on existing files, but it won't do anything to keep Transmission from creating new files with the wrong permissions. I don't know from what you've written whether you mean you have successfully applied the suggested fix to Transmission, or you just mean you have fixed the permissions on the files Transmission already created.

 

As CHBMB suggested, if you tell us which Transmission docker you are using I would be happy to merge this thread with the appropriate support thread if you need further help.

 

Ok, I get it. You're not that motivated to help me. Because that remark is much harder to type than copypasting the right url: https://lime-technology.com/forum/index.php?topic=40300.0

You're right. I'm not at all interested in spoon feeding you every step. I was attempting to give you some of the terms you didn't know you needed, so you could find the information for yourself.

 

The information you didn't have, and I did, was umask and json. Given those terms, you had enough info to solve the problem on your own. I don't use transmission any more, I use deluge, so I didn't remember off the top of my head what the full procedure was. I would have to google it, and reproduce the solution for you based on what others posted.

 

I was trying to help you, but I'll stop if it's not wanted.

  • 2 weeks later...
  • Author

I appreciate the help, but why would you deliberately withhold information? I'm not sure whether I should be thanking you for that.

 

On top of that, unRAID is commercial software, so I expect commercial support - not from you, as you're not an employee.

I appreciate the help, but why would you deliberately withhold information? I'm not sure whether I should be thanking you for that.

 

Why? Well, your attitude would be one darn good reason ;)

 

Except that there was no case of "deliberately withhold information" here, so the question does not really make sense. If you are in need of spoon feeding but only get regular help, try asking for it nicely rather than attacking people helping you. The results might surprise you!

I appreciate the help, but why would you deliberately withhold information? I'm not sure whether I should be thanking you for that.

 

On top of that, unRAID is commercial software, so I expect commercial support - not from you, as you're not an employee.

 

I agree your attitude is somewhat off, you think we hangout here to put up with that?

 

You bought the software, you didn't buy support.  I'm not an employee either, nobody on this thread, all of whom have been trying to help you are, so as you've stated you're not interested in anything any of us have to say I've provided a link for you here.

 

Now also bear in mind, all the transmission containers are created by volunteers, of which I'm a member of one of the more prolific groups creating docker containers and LimeTech don't support them.

On top of that, unRAID is commercial software, so I expect commercial support - not from you, as you're not an employee.

 

So go buy commercial support. Lime-Tech sells personal support sessions. Or send them an email and see what the response is.

 

These public forums are provided by Lime-Tech but nearly all the support you'll find in them are from other consumers who are trying their best to enable others to help themselves if they don't know the exact answer.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.