eg4190

Thanks for the response. So I guess what I really want is for the Dropbox container to run as root. Everything else on my server is running as root and creating downloaded files as root:root, and I've had no issues witht his. I have no personal information on my server and it's just movies, music and comic books, so I really don't care about the security implications of this. If I were to run this Dropbox container under my non-root username, I would also need to move every other container over to that username. So my preference would be to just run this Dropbox container as root. I tried this by entering DROPBOX_USER = root, DROPBOX_USERID = 0, DROPBOX_GROUP = root, and DROPBOX_GROUPID = 0. I'm getting this in the log after activation: usermod: user root is currently used by process 1 WARNING:tornado.access:404 HEAD /blocks/510013235/NV50NTkhIybNc_1--VF0mY4chlBSPeR7fQZwTf1bf4k (172.17.42.1) 678.61ms WARNING:tornado.access:404 HEAD /blocks/510013235/NV50NTkhIybNc_1--VF0mY4chlBSPeR7fQZwTf1bf4k (172.17.42.1) 716.83ms ... ... And so on, with a few thousand of those 404 errors. ... ... Finally, the container dies with this at the end of the log: /usr/local/bin/myinit.sh: line 14: 14 Killed su -l ${DROPBOX_USER} -c "/dropbox/.dropbox-dist/dropboxd" So apparently the container doesn't like running as root, but I'm getting similar 404 errors (minus the first and last error) running as either "nobody" or my non-root UID, just because neither of those accounts has access to the files the other containers are putting in the Dropbox folder.

That's actually something I'm confused about -- I'm assuming all of the other processes are creating new files as root, because none of the other containers specify a user. When I Google how to change the default user for new files, I wind up reading a lot of responses about how doing so is evil. I do have a non-root user account set up on my unRAID box, but I'm not sure how to set that account as the default user for new files, so that all of my other Docker containers are writing to the Dropbox folder as that user (I'm assuming the other containers all have access to the same user accounts as the unRAID box?). Any help would be much appreciated.

I'm getting a weird syncing issue with this container. If I drag/update files into my local Dropbox folder on the various machines I have around the house, the Docker instance on my server is syncing the files properly. But any changes that originate on the server are not being reflected on my local machines. I would like certain automated downloads of mine to move over to Dropbox automatically, but this currently isn't working because the unRAID Docker instance doesn't seem to upload anything. Any ideas?