The paths you wanted i thought were listed on the pic below freefilesync screenshot above.

What paths have you given in the freefilesync template? For remote mounts you might need to give the mounted folder instead of an upper level, and/or edit the path variable and change type to Slave modeĪlso it seems you have a remote mount of itself? What would that be for? Right-clicking in the blank space allows opening other instances. If someone knows a solution ping me in here. As found by below a middle-click will bring up a window list Drag the window a bit to reveal it.Īvoid minimizing the FreeFileSync window as similarly to other containers using this setup there is no way to bring it back. Notes: If the window does not seem to respond to mouse input it's because FreeFileSync's donation popup was spawned behind the main window. The appdata folder is mapped at /home/freefilesync/appdata and will contain logs, config and can be used to store profiles. path2), be sure to only access things through those, writing somewhere else in the container filesystem would fill your Docker image really quickly. 2 paths can be mapped (presented in the container as /home/freefilesync/path1 resp. This image and template based on gives a FreeFileSync instance through a VNC connection. It is available on Windows, Linux and macOS. FreeFileSync is a free and open-source program used for file synchronization.

Freefilesync github