Skip to content
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

Dropbox will soon require ext4 - container currently using ext2 #26

Open
hpka opened this issue Nov 7, 2018 · 15 comments

Comments

Projects
None yet
6 participants
@hpka
Copy link

commented Nov 7, 2018

I've been getting emails recently, which I've just realised are valid, that Dropbox will soon no longer support anything but ext4 (best source from those emails)

The container at least is currently showing:
root@host:/dbox/Dropbox# fsck -N /dev/sdb1 fsck from util-linux 2.25.2 [/sbin/fsck.ext2 (1) -- /dev/sdb1] fsck.ext2 /dev/sdb1 root@host:/dbox/Dropbox#

I'll research as soon as I can how to make the change as I think this is likely more Docker related, but just in case I don't...

@elliottpost

This comment has been minimized.

Copy link

commented Nov 7, 2018

Hi @hpka -- I'm also getting this notification. The server running the container is using ext4, but it looks like the container may be using ext2. My fsck command looks like this:

[root@host Dropbox]# fsck -N /dev/sdb1
fsck from util-linux 2.23.2
[/sbin/fsck.ext2 (1) -- /dev/sdb1] fsck.ext2 /dev/sdb1

Have you seen this PR? #25 I'm thinking of giving it a try but I won't be able to test it immediately. If you do, please let me know if it solves your issue.

@hpka

This comment has been minimized.

Copy link
Author

commented Nov 7, 2018

@elliottpost

This comment has been minimized.

Copy link

commented Nov 7, 2018

@hpka -- I'm going to let my Dropbox install as-is run through the course of tonight and I'll post back tomorrow with if I need to use PR #25 as well. Happy to stay in touch with you on this over the next few days so we can help each other save some time.

@hpka

This comment has been minimized.

Copy link
Author

commented Nov 7, 2018

@Riezebos

This comment has been minimized.

Copy link

commented Nov 8, 2018

In a previous e-mail they said that the new system requirements will go into effect on 7 november 2018. So far it doesn't look like it is being enforced. I am currently using the fix from #25 but in an email from a few days ago Dropbox warned me that here the filesystem is also unsupported.

@stenis999

This comment has been minimized.

Copy link

commented Nov 8, 2018

One of my computers paused syncing due to this, I guess the rest will follow shortly.

Log snippets:

dropbox_1 | Installing new version...
dropbox_1 | Dropbox updated to v61.4.95
dropbox_1 | Starting dropboxd (61.4.95)...
....
dropbox_1 | [ALERT]: So your files continue to sync, sign in to your Dropbox account and move Dropbox to a supported file system.

@Smokex365

This comment has been minimized.

Copy link

commented Dec 20, 2018

I've temporarily forked this project to try and fix the issue. So far, I've got it working by just switching to a ubuntu:xenial bases just to get it working.

https://github.com/Smokex365/docker-dropbox

Update: It seems to work fine with just the base image changed to ubuntu:xenial with only a slight increase in size (~20MB). I tried for hours to get it to work with debian:stretch which I believe would work but I ran into issues with gnupg that I could not resolve and prevented successful builds. I've made a pull request but since the author doesn't seem to be active my fork is also available.

@Riezebos

This comment has been minimized.

Copy link

commented Dec 20, 2018

I've been using https://github.com/djrodgerspryor/docker-dropbox since this issue started and it still works as well for now.

@hjuinj

This comment has been minimized.

Copy link

commented Dec 21, 2018

@stenis999 I experience the same problem as you. Did you manage to find a fix?

Using the containers suggested by @Smokex365 and @Riezebos does not solve this particular problem, do you guys not get the same alert message and see that sync is paused?

@Smokex365

This comment has been minimized.

Copy link

commented Dec 23, 2018

@stenis999 I experience the same problem as you. Did you manage to find a fix?

Using the containers suggested by @Smokex365 and @Riezebos does not solve this particular problem, do you guys not get the same alert message and see that sync is paused?

What error message are you getting? Mine (using my fork) has been running fine so far for days.

@hjuinj

This comment has been minimized.

Copy link

commented Dec 23, 2018

hi @Smokex365 thanks for the response, I think I get the same issue as @stenis999 above. Basically there is not really an error message.
After I execute docker run with this repo or either of the repos you and @Riezebos suggested above, I get this as the last message when I check the logs :

dropbox_1 | [ALERT]: So your files continue to sync, sign in to your Dropbox account and move Dropbox to a supported file system.

Then when I check the status of dropbox inside the container (docker exec -t -i dropbox dropbox status) it indicates Syncing paused

@Riezebos

This comment has been minimized.

Copy link

commented Dec 23, 2018

What kind of filesystem is your Dropbox folder linked to? I don't know if this influences things but for me that is actually ext4 as dropbox wants. It is on a drive encrypted with LUKS. I'm on Ubuntu 18.04.

@hjuinj

This comment has been minimized.

Copy link

commented Dec 23, 2018

Yeah okay I am on centos7 with dropbox volume mapped to xfs filesystem, which is what I have for my local home. I just moved the volume mapping to an external hard drive which has ext4 and now it works again... Although this is not so ideal, is there no chance to use anything other than ext4 anymore?
Either way, thanks for the help :)

@Riezebos

This comment has been minimized.

Copy link

commented Dec 23, 2018

I don't actually know how the fix works, maybe someone can make it work for other base filesystems as well. At least we know what the issue is now!

@Smokex365

This comment has been minimized.

Copy link

commented Dec 25, 2018

Yeah okay I am on centos7 with dropbox volume mapped to xfs filesystem, which is what I have for my local home. I just moved the volume mapping to an external hard drive which has ext4 and now it works again... Although this is not so ideal, is there no chance to use anything other than ext4 anymore?
Either way, thanks for the help :)

yeah, the container still detects the host's file system and xfs isn't supported any longer, only ext4 on linux. You'd probably have to use some kind of volume driver or something to get it to work on anything else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.