Dropbox will soon require ext4 - container currently using ext2 #26
Comments
|
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 [root@host Dropbox]# fsck -N /dev/sdb1
fsck from util-linux 2.23.2
[/sbin/fsck.ext2 (1) -- /dev/sdb1] fsck.ext2 /dev/sdb1Have 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. |
|
That PR looks good but I'm busy too so my testing will also be delayed.
I've also got an ext4 host. I'll try to get to it.
On Wed, Nov 7, 2018, 09:31 Elly Post ***@***.*** wrote:
Hi @hpka <https://github.com/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:
***@***.*** 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
<#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.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AATsLOhL4-gmaPqr7OABswGYDrfmobGDks5usxjbgaJpZM4YS4bL>
.
On Nov 7, 2018 09:31, "Elly Post" <[email protected]> wrote:
Hi @hpka <https://github.com/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
<#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.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AATsLOhL4-gmaPqr7OABswGYDrfmobGDks5usxjbgaJpZM4YS4bL>
.
|
|
Will do.
Dropbox have not given a deadline so not sure how much of a rush this is.
…On Wed, Nov 7, 2018 at 9:51 AM Elly Post ***@***.***> wrote:
@hpka <https://github.com/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 <#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.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AATsLD1crCojv_0IdHEms45Do-2BSsbRks5usx2OgaJpZM4YS4bL>
.
|
|
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. |
|
One of my computers paused syncing due to this, I guess the rest will follow shortly. Log snippets: dropbox_1 | Installing new version... |
|
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. |
|
I've been using https://github.com/djrodgerspryor/docker-dropbox since this issue started and it still works as well for now. |
|
@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. |
|
hi @Smokex365 thanks for the response, I think I get the same issue as @stenis999 above. Basically there is not really an error message.
Then when I check the status of dropbox inside the container ( |
|
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. |
|
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? |
|
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! |
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. |
|
PSA: Dropbox has reverted their stance on this very recently, they now support multiple file systems again. |
|
Hey @Ueland, thanks for letting us know. Can you specify where you saw that? I just checked https://help.dropbox.com/installs-integrations/desktop/system-requirements#linux and it looks like as of today its still only Ubuntu and Fedora. |
|
I only focused on the distro :) |
|
Ah, yes, I see now on https://www.dropbox.com/install-linux it says:
Delightful that support is back, but extremely frustrating that it's a year late |
|
Dropbox reverted their stance but I still get this error message? My host file system is just windows...? The forks above didn't help. |
|
I also still get that error. Running on XFS. Not sure why it still complains. |
|
I think I figured out my issue. While my mapped dropbox folder is an XFS volume, the docker container itself runs on a "cache" disk (on UnRaid) that is btrfs. I don't believe that is supported. I tried mapping more parts of the process to force everything onto the XFS volume, but I'm guessing there's something in the Dropbox daemon that checks the underlying container itself. I've resorted to just running the daemon by itself outside Docker for now. |
|
One last edit here - disregard my last post as well. The root issue was that I was referencing a network share (Samba on Unraid). Once I switched that to a direct path (i.e. /mnt/disk1/dropbox instead of /mnt/user/dropbox), everything started working even within the docker container. Thanks for this great utility! |
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...
The text was updated successfully, but these errors were encountered: