Different ports won't work I think since its a hardcoded port for Dropbox LAN sync (or can't be changed in the headless install). You can delete the mapping on one and that will keep that Dropbox just unable to perform LAN sync.

 

The setting seem good. What does the Dropbox docker log tell you?

 

I should try this later tonight...

 

Here's how I run it, just copied a different file to each dropbox folder and the files appeared in the respective dropbox accounts.

 

 

Next time I reboot I'll check they both link up ok.

hrm, my docker seems to stop uploading to dropbox after a bit of activity, is there anyway to see what it's doing/trying?

You can try this from an ssh terminal to unRAID

root@MediaStore:~# docker exec -it -u nobody Dropbox /bin/bash -l
nobody@7b62d7da15fa:~$ cd Dropbox/
nobody@7b62d7da15fa:~/Dropbox$ dropbox.py status
Up to date
nobody@7b62d7da15fa:~/Dropbox$ dropbox.py ls

This last command should return all green, (don't remember the unsynced color)

then quit with logout

 

You can try this from an ssh terminal to unRAID

root@MediaStore:~# docker exec -it -u nobody Dropbox /bin/bash -l
nobody@7b62d7da15fa:~$ cd Dropbox/
nobody@7b62d7da15fa:~/Dropbox$ dropbox.py status
Up to date
nobody@7b62d7da15fa:~/Dropbox$ dropbox.py ls

This last command should return all green, (don't remember the unsynced color)

then quit with logout

 

Ah HA! yep it's saying "Dropbox isn't running!"

 

I'll try restart it and see what happens

But if I type

dropbox.py start

I get "Dropbox isn't running!" "Dropbox is already running!"

 

I'm splitting off the Dropbox docker image into its own repo. And I've asked to create the support thread: http://lime-technology.com/forum/index.php?topic=46401.0

I just don't want people to see any off the unsupported stuff  and a git branch wasn't going to cut it for me.

 

Squid says he'll add it to CA when he gets home.

 

I really should make a help sheet like CHBMB did. 

But if I type

dropbox.py start

I get "Dropbox isn't running!" "Dropbox is already running!"

 

Did you use a different command to get into the dropbox docker?

Please use:

docker exec -it -u nobody Dropbox /bin/bash -l

This will log you in as nobody, which is the user for running the Dropbox daemon

 

Otherwise the root user running dropbox.py won't talk to the Dropbox daemon.