Permission denied

Nobody has claimed this yet.

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!

Start with the reported Docker command, including the /var/tmp/dropbox_errorqg7annf1.txt path, volume mount, and uid/gid settings. Reproduce the permission error and inspect how the container stores Dropbox data across restarts. Done means the container starts without the permissions error and the account-linking behavior is understood.

Written by the indexing model from the issue text.