[BUG] v1.10.0 docker container broken? #37
Comments
|
in addition, I've reverted to 1.9.0 and the container doesn't restart... |
|
I had the same issue and the same log on a new install. I had to switch to 1.9.0 and turn on DROPBOX_SKIP_UPDATE to get it working. |
|
I'm also getting the same log/error but the DROPBOX_SKIP_UPDATE isn't helping me unless I've implemented that wrong. |
|
@mneimeyer you may have to stop the container and do a Here is my working docker-compose.yml version: "2"
# Need to run on host on new install to be able to watch all files:
# echo fs.inotify.max_user_watches=100000 | sudo tee -a /etc/sysctl.conf; sudo sysctl -p
services:
dropbox:
image: otherguy/dropbox:1.9.0
container_name: dropbox
environment:
- TZ=America/Detroit
- DROPBOX_UID=1000
- DROPBOX_GID=1000
# Can't update Dropbox client or Docker image until this bug is fixed. https://github.com/otherguy/docker-dropbox/issues/37
- DROPBOX_SKIP_UPDATE=true
volumes:
- ./config:/opt/dropbox/.dropbox
- /data:/opt/dropbox/Dropbox
restart: unless-stopped |
|
Thanks everyone for looking into this. I’m extremely busy this week since I’m moving to another state but I will look into it as soon as I can. It looks like it’s related to a new dropbox version (building a new image like 1.10.0 always builds with the latest dropbox version so the skip update flag has no effect). I will need to recreate the build pipeline as well as look into why the latest version of dropbox is failing. Thanks for your patience! |
|
Faced this issue with dropbox client 131.4.3968 trying to use janeczku/dropbox image Then tried your docker image 1.10.0 and observed same go crash described here. Those 2 are most likely related. I confirm reverting to |
|
This doesnt work either. i am getting same error:
|
|
Today my logs tells me, running version 1.9.0 with DROPBOX_SKIP_UPDATE=true: "You're using an old version of Dropbox. Please update within the next 13 days to continue using Dropbox." So that workaround might not work much longer. |
|
Started seeing things not syncing, so yes this workaround is no longer working I think... |
|
...I decided to give 'latest' a go (and without the skip update thing) - and my container updated, then |
|
Same here. The latest image without |
Describe the bug
The container keeps restarting.
Versions:
docker --version):20.10.8, build 3967b7b
docker-compose --version):1.27.4, build 4052192
docker inspect --format='{{.Config.Image}}' [container name])otherguy/dropbox:latest
docker inspect --format='{{.Image}}' [container name])sha256:19b642c36f22217d6e719c0960b37bdda057b5efe155191f36d7d66197431226
docker inspect --format='{{json .Config.Labels}}' [container name])bash: {"com.docker.compose.config-hash":"a51ca3fada082bc4b3d0444a0a0308a1910e1b20831b356954709a35d6044e65","com.docker.compose.container-number":"1","com.docker.compose.oneoff":"False","com.docker.compose.project":"nas","com.docker.compose.project.config_files":"docker-compose.yml","com.docker.compose.project.working_dir":"/NAS","com.docker.compose.service":"dropbox","com.docker.compose.version":"1.27.4","maintainer":"Alexander: File name too long
Run Command:
How did you start the container? If you use
docker-compose, also add your compose file here.docker-compose:
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
I get this in my portainer logs:
The text was updated successfully, but these errors were encountered: