solargis/lsyncd repository overview

⁠Docker containers for syncing files via ssh by lsyncd

This is one way syncing solution so we need source and destination implementation.

• solargis/lsyncd⁠ - docker image for source, with lsync,ssh-client,rsync
• solargis/openssh-server⁠ - docker image fror target, based on linuxserver/openssh-server⁠ with added rsync

Booth images aditionaly contains packages net-tools, tree, vim for easer debuging during trouble shooting. Because services need to be high available.

⁠solargis/openssh-server

See documentation of base image linuxserver/openssh-server⁠.
Plus you can:

• Instead of using enviroment properties PUBLIC_KEY and PUBLIC_KEY_FILE use rather AUTHORIZED_KEYS and AUTHORIZED_KEYS_FILE.
  This properties correctly merge multiple keys (seppareted by new line) to authorized_keys.
  Plus authorized_key can be updated without reboot by command:

  docker exec $container merge-audthorized_keys
  

  Copy

• You can use ssh-entrypoint.sh as command for authorized keys which set default working directory to /data for all ssh connections (works also with lsync, scp, etc.).
  Usage:

  -e AUTHORIZED_KEYS='command="ssh-entrypoint.sh \"${SSH_ORIGINAL_COMMAND:-bash -l}\"" ssh-rsa AAAAXY...Z== comment'
  

  Copy

⁠solargis/lsyncd

Image uses lsyncd preconfiured by docker-entrypoint.sh⁠. Configuration consist of two steps:

1. ssh client with configured by ~/.ssh/config like:

    Host $TARGET_HOST
      User $TARGET_USER
      Port $TARGET_SSH_PORT
      IdentityFile $SSH_KEY_FILE
      CheckHostIP no
   

   Copy
   • Note if SSH_KEY is provided, its contnet is automaticaly strored to file and name of file in SSH_KEY_FILE
   • Records in ~/.ssh/known_hosts is automaticlaly created using HOST_KEY or at startup.
   • This configuration allow to start ssh connection simply by command ssh hostname inside container.
2. lsync config stored in ~/lsyncd.conf.lua like:

    settings {
        statusFile  = "$HOME/lsyncd.status",
        nodaemon    = true,
        insist      = true,
        inotifyMode = "${INOTIFY_MODE:-CloseWrite}",
    }
    sync {
        default.rsyncssh,
        source      = "$SOURCE_PATH:-/var/source", -- source path inside container
        host        = "$TARGET_HOST",
        targetdir   = "$TARGET_PATH", -- path at remote ssh server
        delay       = ${SYNC_DELAY:-0},
        excludeFrom = "$HOME/lsyncd.excludes", -- file automaticaly created from env EXCLUDES
        delete      = "${DELETE:-running}", -- IMPORTAT
        rsync           = {
            archive     = ${RSYNC_ARCHIVE:-true},
            compress    = ${RSYNC_COMPRESS:-false},
        }
    }
   

   Copy
   • Detailned description of config attributes are on pages The Configuration File⁠ and Config Layer 4: Default Config⁠
   • IMPORTATN property sync.delete must by set to running (or false) if multiple sources are synchronized to same target.
   • Property sync.delay allow pospond synchronization n seconds, which optimize synchronization process by invoking rsync less frequent.

⁠Talble of all configuration parameters

⁠Easy setup lsynd by script install-lsyncd

This script allows easy to setup client service running from docker.
Just go to dicrectory wich sould be synchronized and launch command:

install-lsyncd user@host:port:/target/dir -i /path/to/id_rsa --delay=2

⁠Install script install-lsyncd

LASTEST="$(curl -sI https://github.com/solargis/docker-lsyncd/releases/latest | perl -ne '/^Location: .*\/releases\/tag\/(\S+)/i && print $1')";
sudo curl -Ls https://github.com/solargis/docker-lsyncd/releases/download/$LASTEST/install-lsyncd -o /usr/local/bin/install-lsyncd && sudo chmod +x /usr/local/bin/install-lsyncd

⁠Test/example guide

For testing use ./demo.sh which prepares environment and start docker-compose.
Containners in docker-compose.yml works according to this schema:

Usage:

• ./demo.sh setup - prepare envinoment source and target directories, client and host keys, .env file
• ./demo.sh start - call ./demo.sh setup and then start containers by docker-compose up
• ./demo.sh watch - call ./demo.sh start and then start watching source and target directories
• ./demo.sh stop - destory containers by docker-compose down
• ./demo.sh cleanup - call ./demo.sh stop and then remove keys, source and target directories

Note:
Sometimes, after fresh creation of bind directories, the changes are not reflected inside conainer .
If synchronization not works, you can quickly chcek if local files match containers files by executing: ./demo.sh check.
If not, then you simply creacreate containers by ./demo.sh stop && ./demo.sh stop.