-
Notifications
You must be signed in to change notification settings - Fork 28
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
[BUG] Dropbox will rename your existing folder or file named "Dropbox" to finish installing. #60
Comments
I'm getting this aswell |
I'm having this issue as well, if someone finds a work around please share. |
I was getting this when a rebuilt my computer, the work around I used was to copy the Dropbox folder from my the backup I took to my home directory. The container then started ok. |
Running into this same problem. Has anyone here found the solution? This is on a new install, not a backup, so there isn't an existing file I can copy over to make it work. |
Have you tried downloading your files from your Dropbox in the cloud so you have matching folder on your computer ? In essence that all is I did. |
I tried debugging this, but I came up short so far. It seems that something is locking the folder while Dropbox tries to rename it. # rmdir /opt/dropbox/Dropbox/
rmdir: failed to remove '/opt/dropbox/Dropbox/': Device or resource busy After getting # lsof /opt/dropbox/Dropbox/
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
docker-en 1 root cwd DIR 9,1 4096 94504747 /opt/dropbox/Dropbox
sleep 1260 root cwd DIR 9,1 4096 94504747 /opt/dropbox/Dropbox Does the image create the |
Hi, same error for me. |
I am having the same issue. Haven't found a solution yet. |
Also encountering this issue |
Same issue, is there any solution? |
Same issue, no solution so far? |
Same here on Debian 11 |
Same issue on Unraid |
This image exposes a volume for the Dropbox folder, so it is locked. You probably also had a volume mounted there - can't rename that while the container is running. I hit this issue and was frustrated enough to work around it. See my PR for a workaround. It just changes the volumes so that Dropbox can create its own Dropbox folder. It's not a clean solution though; you may need to not mount your Dropbox folder on the first run and then recreate the container with that volume after Dropbox has finished setting up. Hope this helps somebody. I'm up and running again at least. :) |
This is exactly what worked for me. First time start the container without mounting the volume. After having the setting-directory all set up, you can start it with the mount point of the download directory. |
Describe the bug
dropbox | [ALERT]: Dropbox needs to rename your existing folder or file named Dropbox to finish installing. Please close any open documents and try again.
Versions:
docker --version
): Docker version 20.10.12, build e91ed57docker-compose --version
): docker-compose version 1.29.2, build 5becea4cdocker inspect --format='{{.Config.Image}}' [container name]
)docker inspect --format='{{.Image}}' [container name]
)docker inspect --format='{{json .Config.Labels}}' [container name]
)Run Command:
Additional context
I can't find the solution.
The text was updated successfully, but these errors were encountered: