longjin 683e448323 调整配置,启用匿名访问+readonly | há 1 ano atrás | |
---|---|---|
data | há 7 anos atrás | |
Dockerfile | há 1 ano atrás | |
Makefile | há 7 anos atrás | |
README.md | há 7 anos atrás | |
docker-compose.yml | há 1 ano atrás | |
docker-entrypoint.sh | há 7 anos atrás | |
rsyncd.tpl.conf | há 1 ano atrás |
This is a lightweight RSYNC server in a docker container.
This image provides:
A full example is provided in the docker-compose file
git clone https://github.com/mickaelperrin/docker-rsync-server.git
cd docker-rsync-server
docker-compose up
version: '2'
services:
# Example application container, this is where your data is.
app:
image: alpine:3.5
# Simulate an application server with an endless loop.
command: sh -c 'while true; do sleep 10; done';
volumes:
- ./data:/data
# RSYNCD Server
rsyncd:
build: .
image: mickaelperrin/rsyncd-server:latest
environment:
# REQUIRED: For user/password authentication
- USERNAME=sftp
- PASSWORD=password
# REQUIRED: Should be the same as the volume mapping of app container
- VOLUME_PATH=/data
# OPTIONAL: If you want to restrict access to the volume in read only mode. (default false)
- READ_ONLY=false
# OPTIONAL: If you want to chroot the use of rsync. Be sure that your directory structure is compatible.
# See documentation
# (default no)
- CHROOT=yes
# OPTIONAL: customize the volume name in rsync (default: volume)
- VOLUME_NAME=data
# OPTIONAL: restrict connection from (default: 0.0.0.0/0)
- HOSTS_ALLOW=0.0.0.0/0
# OPTIONAL: define the user name or user ID that file transfers to and from that module should take place
# (default set to UID owner of VOLUME_PATH)
# - OWNER_ID = 1000
# OPTIONAL: specifies one or more group names/IDs that will be used when accessing the module. The first one will be the default group, and any extra ones be set as supplemental groups.
# (default set to GID owner of VOLUME_PATH)
# - GROUP_ID = 1000
ports:
- 18873:873
volumes_from:
- app
Configuration is done through environment variables.
Required:
Optionnal:
Besides the usual disclaimer in the license, we want to specifically emphasize that the authors, and any organizations the authors are associated with, can not be held responsible for data-loss caused by possible malfunctions of Docker Magic Sync.
GPLv2 or any later GPL version.