Hi I couldn't find an answer to this question anywhere so please either point me to the right direction or perhaps help me out with this issue.

 

I would sometimes like to edit the config files from different dockers directly instead of going through the UI of the docker in question. 

However I cannot seem to edit these config files directly because it wont allow me to save. What is weird is that I can move the config files to my pc and delete them in the appdata folder.

This way I can at least still edit them on my pc and then copy them back in the appdata folder.. 

Obviously I would like to just be able to modify them directly.

 

I would really appreciate some help. I tried many things including using unraid to fix docker permission.

Firstly never use new permissions on appdata, it breaks stuff.

 

It's a permissions problem.  But you don't say what containers you're using nor which operating system.

Config File Editor plugin

 

https://lime-technology.com/forums/topic/56382-plugin-ca-config-editor/

 

You might need to stop a docker in order to edit a file it's using.

hi sorry I want to edit the home assistant configs (unraid home assistant docker)  but it applies to all dockers I have.

 

nzbget, transmission etc.

 

stopping docker wont resolve this issue.

 

so its a general Unraid permission issue related to the appdata folder. (as far as I can see)

Edited July 26, 20186 yr by BelgarionNL

The config file editor (or nano / vim) should be able to edit any file within appdata, so long as its not read-only.

 

Not being able to modify over the network isn't particularly surprising as most applications have their own unique permission requirements within appdata that may or may not be compatible with the permissions that unRaid uses with respect to network access.

well shit. pardon my french. but that will not work for me because I have to extensively change the configs. so using an browser editor etc wont work.

 

I will try to edit through scp or ftp with ATOM and see if that works.

49 minutes ago, BelgarionNL said:

so its a general Unraid permission issue related to the appdata folder. (as far as I can see)

 

No, it's Linux permissions, and it's heavily dependent on which containers you use.  Unraid by default uses the user nobody in group users.  Not all containers will have their file permissions as nobody:users

 

Then throw into the mix issues with permissions over smb or nfs and it's no wonder you struggle.

 

Running new permissions will change all the file permissions in your appdata to nobody:users but the side effect of this is that this may break the container which is expecting a completely different set of file permissions.

understood wont do that again.

 

apparently winscp works. so I wont see why remote sync with ATOM wont work.

issue resolved:

 

I believe in general this way is far superior than any additional plugins or commandline or whatever:

 

I connect as root to /mnt/user/appdata/home-assistant

 

https://dasmaeh.de/2018/05/28/hassio-configuration-atom/

Sorry to bring this 2-year-old thread up again, but it is exactly the issue I am dealing with at the moment as a new unraid user.

 

Is there an appropriate option to edit the appdata share over smb?

 

I also used the "New Permissions" dialogue, which was working perfect(!) for me, but now i am reading that we should never do that.

editing over smb is just too convenient to give it up for nano via ssh or something like that.