otherguy
[BUG]
Describe the bug
I am fairly new with unraid so there may be something simple I am missing, but After initialconfiguration and connecting to my dropbox successfully, seems to be eternally starting or becomes unresponsive. If I run docker exec -it Dropbox-by-otherguy gosu dropbox dropbox status I get the "Starting..." response.
Versions:
- Docker version 20.10.21, build baeda1f
- Image Name: otherguy/dropbox
- Image ID: sha256:5ca89e6dbcd68c2ed96dae31e6c42c8076cfb663867c5df88dd118fd51758ace
- Labels: (
docker inspect --format='{{json .Config.Labels}}' [container name])
Run Command: -d --name='Dropbox-by-otherguy' --net='bridge' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Sally" -e HOST_CONTAINERNAME="Dropbox-by-otherguy" -e 'DROPBOX_UID'='99' -e 'DROPBOX_GID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/mgutt/unraid-docker-templates/main/mgutt/images/dropbox.png' -v '/mnt/disk3/Dropbox':'/opt/dropbox/Dropbox':'rw' -v '/mnt/user/appdata/Dropbox':'/opt/dropbox/.dropbox':'rw' 'otherguy/dropbox' d60df6a3641cff18482960386533a38552224cf8899b6b5b88fc23de5a9ffaec
Screenshots
Additional context
me too, i have the same problem, and because of this the files are not getting synchronized on the filesystem. also, after stopping and starting the container again, it asks me to connect again to the dropbox account. so somehow it is not connecting as persistent.
Same here. It had worked for years. it's something with docker version and the underlying filesystem because when i remove the data mount it works correctly.
-- update -- After it moved to status indexing, i've stopped the container and remounted the data volume and it continues to sync correctly. So a workaround of sorts exist, although in the relm of voodoo.
I noticed that the container was mounting /opt/dropbox as its own volume, so instead of bind mounting /opt/dropbox/.dropbox and /opt/dropbox/Dropbox I just bind mounted /opt/dropbox, and it's working.
