-
Notifications
You must be signed in to change notification settings - Fork 129
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
Start as root #7
Comments
What volumes does First check that the directory Given that all the above checks out you should be able to run the dropbox container like this (No need to modify users/groups inside the container):
|
The folder
I have verified that symbolic link inside my Dropbox container and files are present. Also, permissions of
I have tried your recommendation of fixing the UID/GID to 1000. I still have the same errors when trying to downloading file : Even if it would have worked, It is not the best way to implement dropbox in my situation, I am planning to attach more than one volumes from more data containers to this Dropbox instance. Data from other volumes can be from different group. It could be nice if we could run Dropbox as root. |
I see. To give Dropbox super privileges (same as running as root) you should just pass
|
So far I have 3 suppositions left :
Any advices are well appreciated. |
What user/permissions is set for "myfile.txt" when you exec into the running dropbox container and check from there? |
Also paste owner/permission of /dbox and /dbox/dropbox from inside the running container! /dbox/Dropbox/srv/docker/company/myapp-data |
From the dropbox container that send to dropbox.com :
From the container that should receive from dropbox.com:
|
Exec to one of the containers where dropbox is running. Then run:
|
No files is synchronized |
Et bien? Ca me dit rien. T'as effectue les activites decrites ci-dessus? |
Je ne comprends pas bien le sens de ce test. |
I think we had a misunderstanding here. I thought the |
I reopen this issue because it is not solved. For Dropbox, it's the client which is not up to date. For you and for me, it is Dropbox client the problem.
Please not that the client crash on every docker instance, after 10 to 20 minutes.
Please do not close the issue until we haven't found the source of the problems. So far I see this possibles issues :
|
Dropbox current linux version available is |
The image has the latest version:
I just had another idea: Apparently dropbox writes error reports to the
|
for some reasons (describe below), I need to test as root user dropbox, is there a simple way to do that?
Reasons:
I have started a container with
--volumes-from=another_data_container
on host A.another_data_container was writing file as uid 1000 gid 1000.
I have added a group with gid 1000 in dropbox, and added dropbox user into the group.
Into
another_data_container
, I have updated folders permissions usingfind . -type d -exec chmod g+rwx
and files permissions usingsfind . -type f -exec chmod g+rw
I linked my dropbox account
file got synced to dropbox (without adding group permissions, dropbox wasn't allowed to upload those files)
I have started a container with
--volumes-from=another_data_container
on host BDropbox container from host B should download
another_data_container
files but I have the following error :Permissions of this file as been uploaded to dropbox with
UID 1000/GID 1000
so for me it should work.The text was updated successfully, but these errors were encountered: