On 11/8/2021 at 11:51 PM, ken-ji said:

Hmm. should be instant, but running `dropbox.py status` should be returning `Syncing...` not `Starting...`
`Starting...` means the daemon is not running correctly...

 

Can you try restarting the container, then running `ps xafu` as the root user inside the container?

Mine returns this

bash-4.3# ps xafu
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root       243  0.2  0.0  18012  3064 pts/0    Ss   05:49   0:00 bash
root       251  0.0  0.0  17684  2216 pts/0    R+   05:49   0:00  \_ ps xafu
root         1  0.0  0.0  17880  2840 ?        Ss   05:43   0:00 /bin/bash /usr/local/bin/dockerinit.sh
nobody      20  5.5  1.3 4839120 444748 ?      Sl   05:43   0:19 /dropbox/.dropbox-dist/dropbox-lnx.x86_64-135.3.4177/dropbox
root        21  0.0  0.0   4376   664 ?        S    05:43   0:00 sleep 86400

 

 

I'm getting the same thing stuck on "Starting...."

I've wiped out all traces of the container and configs and started clean, still happens. No real changes to the docker setup except assigning an IP address and the path to a non-cached share on the array for the Dropbox sync folder.

 

Also, my version is older than the one you show...126.4.4618

 

sh-4.3# su - nobody
nobody@f072e54b0d41:~$ dropbox.py status
Starting...
nobody@f072e54b0d41:~$ exit
logout
sh-4.3# ps xafu
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root       109  0.0  0.0  18012  3060 pts/0    Ss   14:37   0:00 sh
root       128  0.0  0.0  17684  2196 pts/0    R+   14:41   0:00  \_ ps xafu
root         1  0.0  0.0  17884  2848 ?        Ss   14:34   0:00 /bin/bash /usr/local/bin/dockerinit.sh
nobody      21  1.4  0.2 3183312 188496 ?      Sl   14:34   0:06 /dropbox/.dropbox-dist/dropbox-lnx.x86_64-126.4.4618/dropbox
root        22  0.0  0.0   4376   668 ?        S    14:34   0:00 sleep 86400
sh-4.3# 

 

the log only shows this from the creation of the container:

 

chown: cannot access '/dropbox/.dropbox': No such file or directory,
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-126.4.4618/cryptography.hazmat.bindings._openssl.cpython-38-x86_64-linux-gnu.so',
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-126.4.4618/cryptography.hazmat.bindings._padding.cpython-38-x86_64-linux-gnu.so',
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-126.4.4618/psutil._psutil_linux.cpython-38-x86_64-linux-gnu.so',
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-126.4.4618/psutil._psutil_posix.cpython-38-x86_64-linux-gnu.so',
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-126.4.4618/apex._apex.cpython-38-x86_64-linux-gnu.so',
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-126.4.4618/tornado.speedups.cpython-38-x86_64-linux-gnu.so',
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-126.4.4618/wrapt._wrappers.cpython-38-x86_64-linux-gnu.so',
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-126.4.4618/PyQt5.QtWidgets.cpython-38-x86_64-linux-gnu.so',
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-126.4.4618/PyQt5.QtCore.cpython-38-x86_64-linux-gnu.so',
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-126.4.4618/PyQt5.QtGui.cpython-38-x86_64-linux-gnu.so',
This computer isn't linked to any Dropbox account...,
Please visit https://www.dropbox.com/cli_link_nonce?nonce=20044a5727078b85e3cdd9457a105b5e to link this device.,
This computer isn't linked to any Dropbox account...,
Please visit https://www.dropbox.com/cli_link_nonce?nonce=20044a5727078b85e3cdd9457a105b5e to link this device.,
This computer is now linked to Dropbox. Welcome Ross

 

Any ideas? I never see any of the stuff like this in the logs (copied from other posts here, never see this on my system)-

 

dropbox: initializing
dropbox: initializing python 3.7.9
dropbox: setting program path '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-109.4.517/dropbox'
dropbox: setting python path '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-109.4.517:/dropbox/.dropbox-dist/dropbox-lnx.x86_64-109.4.517/python-packages.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: enabling allocator metrics
dropbox: applying overrides
dropbox: running main script

 

thanks Ken-ji here is what i get

 

 

Edited November 12, 20214 yr by Tom Roskilly
better info added

Hmm, I'm stumped.

I'll check to see if there's anything in the Dropbox headless client - they really don't give it as much support as they should.

I dont suppose it has something to do with the network type?

On 11/13/2021 at 12:43 AM, ken-ji said:

Hmm, I'm stumped.

I'll check to see if there's anything in the Dropbox headless client - they really don't give it as much support as they should.

 

I have same issues. I install as new container and the dropbox still after starting in "Starting..." status. I am checjing this status via commad "dropbox.py status" in consle of Dropbox.

 

Do you have any ideas why the Dropbox not start syncing?

 

Many thanks

I finally got it working in bridge mode by specifying dropbox version 1.9 and setting dropbox_skip_update to true in extra parameters 

My container dropbox have setting to bridge mod. I add variable "dropbox_skip_update" set to "true". But still not syncing...

Where can I specify dropbox to version 1.9?

Sorry that's my mistake. I forgot that I swapped repositories too, so it's probably not a valid post here. However, I think the second repository I tried had the exact same issues that we were experiencing with roninkenji's So there might be a clue in there somewhere for you Kenji. I'm not knowledgable enough to work it out, sorry.

Anyway, after deleting the container, image and files in appdata I put otherguy/dropbox:1.9.0 in the repository field, put the extra parameters info in and followed the instructions as normal. 

I really appreciated the speedy responses from you Kenji. Please let me know if you'd like me to test out your repository again, if you make any changes. 

Great! I delete container. I set new one container from repo otherguy/dropbox:1.9.0. I set variables and paths and it`s working!!

 

If Kenji`s container will be update for working state then I can it try again.

 

Thanks Tom!

Edited November 21, 20214 yr by Ropo

I've pushed a new version of my dropbox image containing the current version of dropbox.

I've had to work out how to automate building - now that Docker autobuilds are a paid option. and I didn't want to move off docker.io registry for the time being.

after update, here is my log file, it's not starting up. stuck.

 

deleted docker, remove link to dropbox, deleted the appdata dropbox directory, reinstalled dropbox, relink to drop box, working again.

On 2/8/2016 at 4:04 PM, ken-ji said:

Add the docker and configure the folders:

refer to attachment: Container Mounts.png

 

Then check the docker container logs for a link to copy and paste to link your dropbox container.

I do not understand how to add the link that I am getting via the log.

 

As soon as I am clicking on the link and basically linking unRIAD Dropbox to my Dropbox account I am getting another error (please see screenshot).

Edited June 28, 20251 yr by EdgarWallace

Show your docker mappings here and check them for a folder named Dropbox - that sounds like the source of the issue.

On 3/23/2022 at 12:49 PM, ken-ji said:

Show your docker mappings here and check them for a folder named Dropbox - that sounds like the source of the issue.

 

I've got the same issue. Completely fresh install, installed the app using the default settings and linked to Dropbox and then just have this:
 

[ALERT]: Dropbox needs to rename your existing folder or file named Dropbox to finish installing. Please close any open documents and try again.

 

My settings are the same as EdgarWallace

I think it is the folder in /appdata/dropbox called Dropbox. As I can replicate this error even if I use a different folder name for the location of my files and lower case the container folder. 

Sorry guys, real life's been busy. I'll look into this soon over the weekend.

I'm getting the same issue

[ALERT]: Dropbox needs to rename your existing folder or file named Dropbox to finish installing. Please close any open documents and try again.

 

Any update on this or is it unusable?

Quote

[ALERT]: Dropbox needs to rename your existing folder or file named Dropbox to finish installing. Please close any open documents and try again.

 

I have just tried to install this for the first time and I am also seeing the same error. I have tried both this and the "otherguy" repository, with both cache only and single disk. Is there any chance of a fix for this?

When you switched repositories, was it an entirely fresh install? Also, what is in your Repository and Docker Hub URL fields? 

Fresh install (i.e. remove container, image and appdata folder) on both. The repository/hub fields for each:

 

roninkenji/dropbox-docker

https://hub.docker.com/r/roninkenji/dropbox-docker/

 

and

 

otherguy/dropbox

https://hub.docker.com/r/otherguy/dropbox
 

Each time: I install, check the logs, it asks me to click a link to authenticate, I do so, it begins spamming the aforementioned alert and nothing ever syncs.

Looks like something changed and this is no longer working. When I try to authenticate I get this

 

You're using an old version of Dropbox. Please download the latest version at www.dropbox.com/downloading

 

 

I got that message a while back, but took a chance and removed "TRUE" from the DROPBOX_SKIP_UPDATE: field.

After a few attempts this worked for me, but I had to rename the location of my Dropbox user files, to create a fresh copy of my files, it seemed to get stuck otherwise.

 

On 6/16/2023 at 5:36 AM, Tom Roskilly said:

I got that message a while back, but took a chance and removed "TRUE" from the DROPBOX_SKIP_UPDATE: field.

After a few attempts this worked for me, but I had to rename the location of my Dropbox user files, to create a fresh copy of my files, it seemed to get stuck otherwise.

 

 

Hi Tom. Thanks for sharing your experience. Could you share how you did to "removed "TRUE" from the DROPBOX_SKIP_UPDATE: field"? I'm a new and amateur user, and it would be very useful to me. Thank you very much!

Hi vmontserrat "DROPBOX_SKIP_UPDATE" variable set as "True" (Manually entered into the Extra Parameters area) was a fix we used a while back, when the latest Dropbox version was throwing errors.

To give context, we had to use a different repository from otherguy, when ken-ji's version was no longer able to connect to Dropbox.

Unfortunately, the other repository had issues as well and so we had to force it not to update. 

If you are starting afresh, then DROPBOX_SKIP_UPDATE might not apply to you.