Dropbox not working #40
Comments
|
Until my PR may get merged you can use my fork and build your own image (just replace
|
|
Big thanks. |
|
Hmm... $ docker build --force-rm --tag dropbox https://github.com/thomashilzendegen/docker-dropbox.git#libatomic-fix $ git clone https://github.com/thomashilzendegen/docker-dropbox.git#libatomic-fix What am I doing wrong? |
Nothing... This works for me. Maybe your git version is too old? Mine is |
|
I'm getting an error due to a PGP key not being able to be retrieved. This is from a CentOS 7.7 machine. docker logs --follow agitated_wing Removing intermediate container 207e05067524 |
I got this too from time to time. I just repeated the build until it worked. |
|
On windows (I'm at work)...
|
Yeah it looks like the pgp.mit.edu keyserver is down, when I try to retrieve the key manually it gives "The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later." |
When cloning by yourself you should omit the branch part ( |
|
I know. I decided to try after failed "docker build ...". |
|
OK the MIT keyserver finally came back on line. But now this: Step 8/14 : RUN mkdir -p /opt/dropbox && mv /dbox/.dropbox-dist/dropbox-lnx* /opt/dropbox/ && mv /dbox/.dropbox-dist/dropboxd /opt/dropbox/ && mv /dbox/.dropbox-dist/VERSION /opt/dropbox/ && rm -rf /dbox/.dropbox-dist && install -dm0 /dbox/.dropbox-dist && chmod u-w /dbox && chmod o-w /tmp && chmod g-w /tmp && mv /usr/bin/dropbox /usr/bin/dropbox-cli mv: cannot remove '/dbox/.dropbox-dist/dropbox-lnx.x86_64-85.4.155/ACKNOWLEDGEMENTS': No such file or directory Removing intermediate container 45e372403c3d I'm a Docker novice - not sure how to recover here. |
|
hey any news about fixing the main build ? |
git version 1.8.3.1 (CentOS Linux release 7.7.1908 (Core)). |
Ok, just clone it manually with |
|
has anyone been able to build with Thomas recomendations ? I am struggling to get it done... it keeps complaining about the keys: gpg: requesting key 5044912E from hkp server pgp.mit.edu ---- EDIT ---- Image built OK. Now the issues I am getting are inside the container when running it. I see that the 'run' script sets this permissions, but I can't understand why its not working as it should... I created the image by running: I remember having to put GID 0 before this issue to get it syncing... but still not working with that... I am a complete noob with docker, and I would like to troubleshoot the error, but of course the container dies / restart. Any help ? Thanks! |
|
Well guys, I fixed the permissions issue as well... When giving the volumes path, add a :Z at the end... Like this: I got rid of the permissions issues in the shared directories by adding that. In case you had issues with the image creation and permissions, with my last two posts you should be able to fix it. Thanks! |
|
I'm having an issue where file syncing stops after about 12 hours. Usually after 11pm local time (US Pacific). |
|
I think I'm done with dropbox forever. I managed to get a build to go by modifying the Dockerfile but then I ran back into the "UnicodeDecodeError" problem when I type dropbox status that I couldn't fix. Also, the permissions issue on those shared libraries still requires a "docker exec chmod" type solution. It sucks but dropbox is just crap for Linux any more. I am looking into nextcloud. |
|
This is indeed very sad. My use case requires a smartphone app that can play video files. Seems nextcloud doesn't support that. |
|
If you are having issues with the "pgp.mit.edu" keyserver, try using "hkp://pool.sks-keyservers.net:80" instead. That server seems to be more reliable. |
|
Yeah, I got past the pgp key server issue by finding another "mirror" key server. The problem I had was with file syncing stopping (and no errors logged) after a few hours and container needed to be restarted. So I had the idea of just restarting the container every 4 hours, but then one of the dropbox folders got into an inconsistent state: The folder was renamed "irreconcilable" or something similar, and did not self-heal. Pretty dicey. So now I have Dropbox on Windows (yuck) serving a dropbox folder with NFS, and my linux machine as NFS client mounting that dropbox folder. Syncing is OK again, but for how long... |
|
The UnicodeDecode error is due to the Docker instance not having a locale set. To fix it without having to change the dropbox-cli file:
Now Python has no character encoding issues as it will use UTF-8. Here is my version: RUN apt-get -qqy update ENV LANG en_US.UTF-8 Change en_US to whatever locale your system uses. |
|
It's clear to me that janeczku has abandoned this project, as he hasn't changed anything on the main branch in over three years. Someone really needs to fork this and incorporate all these pending changes. |
|
@adamkdean (for #38) and @thomashilzendegen (here) have both created forks to address the recent failures. |
|
Indeed, there are 100 forks, LOL. I am kind of a github newbie. It would be nice however to know which fork is the most up to date with the outstanding issues. |
@thomashilzendegen, can you create another hub on dockerhub based on yor fork? |
|
I have published a fork: https://hub.docker.com/r/otherguy/dropbox/ (GitHub repo here: https://github.com/otherguy/docker-dropbox) I also updated to the latest |
|
This is work for me. Changes key server address in DockerFile. and then build. |
|
Same on 86.4.146 I'm proceeding with a fork. Following error dump is just in case it helps someone else |
|
@Joshfindit did you try this fork: https://hub.docker.com/r/otherguy/dropbox/ |
I did not. This is for a production server and no offence to @otherguy the name (and personal website) does not give me the impression that it will be maintained going forward. |
|
@Joshfindit sure, that's your prerogative :) Thank you for your criticism of my name and "personal website", I do welcome pull requests if you improve on my version! |
|
Regarding libatomic issue, i just solved it by installing libatomic1: RUN apt-get update && apt-get install libatomic1 Just add this installation in Dockerfile. I work over ubuntu:latest, probably future releases of dropbox will fix this issue for ubuntu minimal on docker. |
@thomashilzendegen I did this some time ago successful, and today I looked at the dropbox status again and the container fails to start with the following errors: After executing Which includes the line Why does the container still fails to start? |
|
I'm also seeing this Update: I'm pushing the fix for this to Update: Can confirm the fix is now working for my systems that use this image. |
|
@janeczku, @adamkdean it works for me as well |
Yesterday, the dropbox in the container was updated to version 85.4.155. And it does not start anymore. CentOS 7.
Error: ImportError: libatomic.so.1: cannot open shared object file: No such file or directory.
Detailed:
!! dropbox: fatal python exception:
['Traceback (most recent call last):\n', ' File "dropbox/client/main.pyc", line 7919, in main\n', ' File "dropbox/client/main.pyc", line 7843, in main_startup\n', ' File "dropbox/client/main.pyc", line 942, in init\n', ' File "dropbox/sync_engine_boundary/factory.pyc", line 147, in make_default_file_system\n', ' File "dropbox/sync_engine_boundary/factory.pyc", line 99, in init\n', ' File "dropbox/sync_engine_boundary/factory.pyc", line 118, in _initialize_classes\n', ' File "dropbox/sync_engine/nucleus/classic_client/sync_engine.pyc", line 276, in \n', ' File "dropbox/sync_engine/nucleus/classic_client/thin_adapter/in_proc.pyc", line 98, in \n', ' File "dropbox/sync_engine/nucleus/classic_client/wrapped_thin_client.pyc", line 26, in \n', ' File "dropbox/sync_engine/nucleus/thin_client/client.pyc", line 28, in \n', ' File "dropbox/foundation/metrics/amp/remote_sink.pyc", line 10, in \n', 'ImportError: libatomic.so.1: cannot open shared object file: No such file or directory\n'] (error 3)
The text was updated successfully, but these errors were encountered: