Docker/Rsync: Difference between revisions
From charlesreid1
No edit summary |
|||
| Line 9: | Line 9: | ||
* The Makefile contains a call to the docker build and docker run scripts, and tells the user to open the firewall. | * The Makefile contains a call to the docker build and docker run scripts, and tells the user to open the firewall. | ||
* The build script just calls docker build | * The build script just calls docker build | ||
* The | * The run script calls docker run, and connects the host and container port. It also sets a host directory to mount as a volume. This directory should contain whatever is being rsync'ed. | ||
Link to the Makefile: https://charlesreid1.com:3000/docker/d-rsync | Link to the Makefile: https://charlesreid1.com:3000/docker/d-rsync | ||
| Line 17: | Line 17: | ||
Link to run script: https://charlesreid1.com:3000/docker/d-rsync/src/master/run_rsync.sh | Link to run script: https://charlesreid1.com:3000/docker/d-rsync/src/master/run_rsync.sh | ||
Link to rsync configuration script <code>/etc/rsyncd.conf</code>: https://charlesreid1.com:3000/docker/d-rsync/src/master/rsyncd.conf | |||
Note: if you have a <code>/etc/rsyncd.conf</code> file in place on the docker host machine, rsync will probably be one of the services that starts on boot. To stop the host rsync from starting on boot, run: | |||
<pre> | |||
$ rm /etc/init.d/rsync | |||
</pre> | |||
=Flags= | =Flags= | ||
Revision as of 06:16, 9 April 2017
Docker container running rsync: https://charlesreid1.com:3000/docker/d-rsync
Purpose
The purpose of running rsync in a docker container is for consistency - we are already running an stunnel docker container, listening for the rsync traffic, so I wanted to run the rsync server in a container as well.
Basic workflow is as follows:
- Makefile is where the user starts/executes commands
- The Makefile contains a call to the docker build and docker run scripts, and tells the user to open the firewall.
- The build script just calls docker build
- The run script calls docker run, and connects the host and container port. It also sets a host directory to mount as a volume. This directory should contain whatever is being rsync'ed.
Link to the Makefile: https://charlesreid1.com:3000/docker/d-rsync
Link to build script: https://charlesreid1.com:3000/docker/d-rsync/src/master/build_rsync.sh
Link to run script: https://charlesreid1.com:3000/docker/d-rsync/src/master/run_rsync.sh
Link to rsync configuration script /etc/rsyncd.conf: https://charlesreid1.com:3000/docker/d-rsync/src/master/rsyncd.conf
Note: if you have a /etc/rsyncd.conf file in place on the docker host machine, rsync will probably be one of the services that starts on boot. To stop the host rsync from starting on boot, run:
$ rm /etc/init.d/rsync
Flags
 |
docker notes on the virtual microservice container platform
Installing the docker platform: Docker/Installing Docker Hello World: Docker/Hello World
Creating Docker Containers: Getting docker containers from docker hub: Docker/Dockerhub Creating docker containers with dockerfiles: Docker/Dockerfiles Managing Dockerfiles using git: Docker/Dockerfiles/Git Setting up Python virtualenv in container: Docker/Virtualenv
Running docker containers: Docker/Basics Dealing with volumes in Docker images: Docker/Volumes Removing Docker images: Docker/Removing Images Rsync Docker Container: Docker/Rsync
Networking with Docker Containers:
|
|
docker pods pods are groups of docker containers that travel together
Docker pods are collections of Docker containers that are intended to run in concert for various applications.
Wireless Sensor Data Acquisition Pod The wireless sensor data acquisition pod deploys containers This pod uses the following technologies: Stunnel · Rsync · Apache · MongoDB · Python · Jupyter (numerical Python stack)
Deep Learning Pod This pod utilizes the following technologies: Python · Sklearn · Jupyter (numerical Python stack) · Keras · TensorFlow
|