5 hours ago, Djoss said:

What do you mean by "automatic compare" ?

Hi!

The moment you start the docker container, FreeFileSync starts to compare the folders from the last sync session. The destination folder is not available all the time. This causes the drives in unraid to spin up, to access the source folders, and then an error message appears when the destination folders are unreachable.

The knock on problem it then causes is that the drives will not spin down again, since it is in use, and you have to log in and cancel the "comparison" before your unraid server will spin down the drives and quiet down.

I have FreeFileSync on my Windows PC, and it does not have this behavior. I think there is a setting somewhere that toggles this "compare at startup" behavior. I can't see or find the option in the UI of the docker version.

Hope this makes more sense now.

Any help to get this disabled will be greatly appreciated.

Thanks!

I don't see this problem on my side. Nothing is done automatically when the container starts.

Could you share a screenshot of the UI showing the problem ? Is it really the main FreeFileSync instance that is doing the comparison and not one of the scheduled job ?

5 hours ago, Djoss said:

I don't see this problem on my side. Nothing is done automatically when the container starts.

Could you share a screenshot of the UI showing the problem ? Is it really the main FreeFileSync instance that is doing the comparison and not one of the scheduled job ?

Hi,

Thanks for getting back to me. I will make a screen recording of this and share it as soon as possible. It was doing this from the start. I have one scheduled job, but that was set up later and after the fact. I'll disable it just to make sure. I'll get back to you.

With thanks,

Wietsche

Hello,
I just submitted a bug report on Github for an unrelated issue (regarding Japanese fonts), but was reading this thread.

Actually, I also experience the same issue as @Wietsche , as well.

If any paths are left filled in for the folder pair bars of [Last Session], the container will automatically run a Compare on these folder pairs on startup.

My workaround has been to be careful to clear out the paths or to click "New Config" before shutting down the container, but I agree, it would be nice if this wasn't an issue.

For what it's worth, I don't have any scheduled jobs or saved configs and have been typing in paths and running all my syncs manually for the time being, so I don't think this issue is related to cron/batch jobs.

(And again, thank you for your work maintaining this container. It's awesome!)

Edited June 5, 20251 yr by wabun

3 hours ago, wabun said:

Hello,
I just submitted a bug report on Github for an unrelated issue (regarding Japanese fonts), but was reading this thread.

Actually, I also experience the same issue as @Wietsche , as well.

If any paths are left filled in for the folder pair bars of [Last Session], the container will automatically run a Compare on these folder pairs on startup.

My workaround has been to be careful to clear out the paths or to click "New Config" before shutting down the container, but I agree, it would be nice if this wasn't an issue.

For what it's worth, I don't have any scheduled jobs or saved configs and have been typing in paths and running all my syncs manually for the time being, so I don't think this issue is related to cron/batch jobs.

(And again, thank you for your work maintaining this container. It's awesome!)

Thanks @wabun ! Exactly that. Glad it was not just me.

I am also very appreciative of this docker container! Thanks for the work!

Please have a look if this can be fixed. If one needs automatic syncing, that functionality should be accessed with scheduled jobs.

Cheers,

W

Ok I was also able to reproduce my side. Since this is a behaviour of FreeFileSync itself, you should also ask on its forum: https://freefilesync.org/forum/

I can also check its source code to see if this is something than can be easily deactivated.

Edited June 7, 20251 yr by Djoss

I found the source of the problem. This will be fixed with next version of the image.

18 minutes ago, Djoss said:

I found the source of the problem. This will be fixed with next version of the image.

Fantastic!

Thank you very much!

On 6/7/2025 at 7:58 PM, Djoss said:

I found the source of the problem. This will be fixed with next version of the image.

Hi!

I can confirm that this is now resolved. Thank you so much!

Cheers!

W

Thank you for putting this Docker together. I've been using the Windows version for years. Would anyone know how to activate the email notifications and p[performance improvements we earn from our donations to the FreeFileSync project?

4 hours ago, Optimus Prime said:

Thank you for putting this Docker together. I've been using the Windows version for years. Would anyone know how to activate the email notifications and p[performance improvements we earn from our donations to the FreeFileSync project?

This container integrates the free/opensource version. The donation edition is a different software, for which the source code is not available and the binary cannot be distributed.

Hi,

How can this be fixed?

// Frode

8 hours ago, frodr said:

Hi,

How can this be fixed?

// Frode

Looks like a folder permission issue. What are permissions the "media/serier" folder ?

11 hours ago, Djoss said:

Looks like a folder permission issue. What are permissions the "media/serier" folder ?

Thanks, changing permissions fixed it.

not sure why i sometimes get EPERM: Operation not permitted [chown] on some files despite setting the container as privileged. isn't free file sync supposed to copy the file across, so permission on the file is irrelevant?

Update, need to set the user id and group id to 0 to enable the container to run as root, as it will work.

Edited October 18, 2025Oct 18 by Goldmaster

Hi !

This docker no longer aivable on Apps by CA:

How can we install it now ?

Thanks ;)

It's back now :)

Thanks.

How can we install it without internet ?

I wanted to install it off line. How to download a package to install after ?

Thanks.

You want to install the docker container without internet ?

Is there anyway to check if the cron jobs are actually working? I see both I have listed in the ffs cron file, but I see no evidence the process actually ran in any log.