You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Couldn't start Dropbox.
This is usually because of a permissions error. Storing your home folder on a network share can also cause an error.
Get more help at https://www.dropbox.com/c/help/permissions_error
Please contact Dropbox support with the following info for help:
/var/tmp/dropbox_errorqg7annf1.txt
I presume that I'm supposed to run with -v ~homedir/Dropbox/:/dbox/Dropbox to do the mount. I've tried the run command with various combinations of the uid/gid environment variables, all with the same negative result.
Do I have to re-link the Dropbox account every time I run the container? If so, then I have to manually intervene every time my host is re-started (and thus the container is re-started). Am I missing something?
Since Dropbox dropped support for my O/S, it would be very helpful to actually use Dropbox this way. Thanks!
The text was updated successfully, but these errors were encountered:
You don't need to link the account each time if you store the credentials outside the container. My setup looks like this:
/dbox/Projects
/dbox/Public
/dbox/Private
And my containers are started like this:
docker run
--detach=true
--volume=/dbox/Projects:/dbox/Dropbox
--restart=always
--net=host
--name=projects
janeczku/dropbox
docker run
--detach=true
--volume=/dbox/Public:/dbox/Dropbox
--restart=always
--net=host
--name=public
janeczku/dropbox
docker run
--detach=true
--volume=/dbox/Private:/dbox/Dropbox
--restart=always
--net=host
--name=private
janeczku/dropbox
Doing it that way requires linking each docker container to your account, which may or may not be what you want. I do it that way because I am using different accounts for each container. If you want to use the same account for each container, you have to share the credentials.
Sharing credentials is supposed to be done like this:
docker logs dropbox shows:
Couldn't start Dropbox.
This is usually because of a permissions error. Storing your home folder on a network share can also cause an error.
Get more help at https://www.dropbox.com/c/help/permissions_error
Please contact Dropbox support with the following info for help:
/var/tmp/dropbox_errorqg7annf1.txt
I presume that I'm supposed to run with -v ~homedir/Dropbox/:/dbox/Dropbox to do the mount. I've tried the run command with various combinations of the uid/gid environment variables, all with the same negative result.
Do I have to re-link the Dropbox account every time I run the container? If so, then I have to manually intervene every time my host is re-started (and thus the container is re-started). Am I missing something?
Since Dropbox dropped support for my O/S, it would be very helpful to actually use Dropbox this way. Thanks!
The text was updated successfully, but these errors were encountered: