Last updated: 2 Nov 26 05:22:35 (UTC)

Yes, exactly. Docker supports this through a feature called bind mounts.

Yes, exactly. Docker supports this through a feature called bind mounts. You can install the FreeFileSync Donation Edition on the Linux host and make that installation accessible inside a Docker container without copying the files into the Docker image.

The container can then execute the FreeFileSync binaries directly from the host-mounted directory.

How it would work

Linux host (Ubuntu or Mint)

/opt/FreeFileSync/ — Donation Edition binaries

~/.config/FreeFileSync/ — configuration and activation data

Docker bind mounts

Docker container (Ubuntu-based)

/opt/FreeFileSync/ — mounted from host

/home/ffs/.config/FreeFileSync/ — mounted from host

Runs the host’s Donation Edition executable

For example, assuming FreeFileSync is installed in /opt/FreeFileSync on the host:

docker run -it \
  --mount type=bind,src=/opt/FreeFileSync,dst=/opt/FreeFileSync,readonly \
  --mount type=bind,src="$HOME/.config/FreeFileSync",dst=/root/.config/FreeFileSync \
  ubuntu:24.04 bash

Once inside the container, you could attempt to launch it with:

/opt/FreeFileSync/FreeFileSync

This is a conceptual example. The container would still need the necessary shared libraries, graphical display access (if using the GUI), and permissions.

Three important considerations

  • Activation: Mounting the configuration directory makes the host’s activation information available, but it doesn’t guarantee that FreeFileSync will recognize the container as the same activated machine.

  • Compatibility: The container must have compatible Linux libraries. An Ubuntu-based container is preferable to Alpine for an Ubuntu/Mint installation.

  • Licensing: The Donation Edition’s licensing and device limits still apply. A bind mount does not bypass activation requirements.

One additional advantage

If FreeFileSync is updated on the Linux host, the container can immediately access the updated executable because it is using the same installation directory.

So your understanding is correct: You can run the FreeFileSync Donation Edition installed outside Docker from inside Docker, provided the runtime dependencies are available. The only significant uncertainty is whether its existing activation will remain valid inside the container.