Rsync/Docker: Difference between revisions
From charlesreid1
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
The rsync docker container acts as a kind of void function: it modifies (updates) files on disk, based on the traffic on port 873, but it does not result in any traffic being sent out, so it "returns" nothing. | The rsync docker container acts as a kind of void function: it modifies (updates) files on disk, based on the traffic on port 873, but it does not result in any traffic being sent out, so it "returns" nothing. | ||
This is the line in the rsyncd.conf file that does that: | |||
<pre> | <pre> | ||
hosts allow = 127.0.0.1 | |||
</pre> | </pre> | ||
When we run the rsync docker image, it needs to have access to the directory it is supposed to update in the host file system. Mount volumes when running the docker image with docker run -v flag: | |||
<pre> | |||
$ docker run -v /host/dir:/container/dir | |||
</pre> | |||
In our case, both host and container dir is <code>/wifi</code>. | |||
Latest revision as of 07:20, 5 April 2017
rsyncd.conf man page: https://linux.die.net/man/5/rsyncd.conf
Default port for rsync is 873.
Link to rsync docker container files: https://git.charlesreid1.com/docker/d-rsync
The rsync docker container acts as a kind of void function: it modifies (updates) files on disk, based on the traffic on port 873, but it does not result in any traffic being sent out, so it "returns" nothing.
This is the line in the rsyncd.conf file that does that:
hosts allow = 127.0.0.1
When we run the rsync docker image, it needs to have access to the directory it is supposed to update in the host file system. Mount volumes when running the docker image with docker run -v flag:
$ docker run -v /host/dir:/container/dir
In our case, both host and container dir is /wifi.