vincent/eea.docker.rsync
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update Readme.md

Browse Source
This commit is contained in:
valentinab25 2018-03-16 11:18:39 +02:00 committed by GitHub
parent 0d31234101
commit 73feb85ed0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 31 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
Readme.md
View File

@ -49,3 +49,34 @@ Bring the `file` on client:
$ docker exec -it rsync_client sh
$ rsync -e 'ssh -p 2222' -avz root@foo.bar.com:/data/ /data/
$ ls -l /data/
### Rsync data between containers in Rancher
0. Request TCP access to port 2222 to an accessible server of environment of the new installation from the source container host server.
1. Start **rsync client** on host from where do you want to migrate data (ex. production).
Infrastructures -> Hosts -> Add Container
* Select image: eeacms/rsync
* Command: sh
* Volumes -> Volumes from: Select source container
2. Open logs from container, copy the ssh key from the message
2. Start **rsync server** on host from where do you want to migrate data (ex. devel). The destination container should be temporarily moved to an accessible server ( if it's not on one ) .
Infrastructures -> Hosts -> Add Container
* Select image: eeacms/rsync
* Port map -> +(add) : 2222:22
* Command: server
* Add environment variable: SSH_AUTH_KEY="<SSH-KEY-FROM-R-CLIENT-ABOVE>"
* Volumes -> Volumes from: Select destination container
3. Within **rsync client** container from step 1 run:
```
$ rsync -e 'ssh -p 2222' -avz <SOURCE_DUMP_LOCATION> root@<TARGET_HOST_IP_ON_DEVEL>:<DESTINATION_LOCATION>
```
4. The rsync servers can be deleted, and the destination container can be moved back ( if needed )