$ oc rsync <source> <destination> [-c <container>]
You can use the CLI to copy local files to or from a remote directory in a container. This is a useful tool for copying database archives to and from your pods for backup and restore purposes. It can also be used to copy source code changes into a running pod for development debugging, when the running pod supports hot reload of source files.
Support for copying local files to or from a container is built into the CLI:
$ oc rsync <source> <destination> [-c <container>]
For example, to copy a local directory to a pod directory:
$ oc rsync /home/user/source devpod1234:/src
Or to copy a pod directory to a local directory:
$ oc rsync devpod1234:/src /home/user/source
Use oc rsync
to copy database archives from an existing database container
to a new database container’s persistent volume directory.
MySQL is used in the example below. Replace |
Back up the existing database from a running database pod:
$ oc rsh <existing db container> # mkdir /var/lib/mysql/data/db_archive_dir # mysqldump --skip-lock-tables -h ${MYSQL_SERVICE_HOST} -P ${MYSQL_SERVICE_PORT:-3306} \ -u ${MYSQL_USER} --password="$MYSQL_PASSWORD" --all-databases > /var/lib/mysql/data/db_archive_dir/all.sql # exit
Remote sync the archive file to your local machine:
$ oc rsync <existing db container with db archive>:/var/lib/mysql/data/db_archive_dir /tmp/.
Start a second MySQL pod into which to load the database archive file created above.
The MySQL pod must have a unique DATABASE_SERVICE_NAME
.
$ oc new-app mysql-persistent \ -p MYSQL_USER=<archived mysql username> \ -p MYSQL_PASSWORD=<archived mysql password> \ -p MYSQL_DATABASE=<archived database name> \ -p DATABASE_SERVICE_NAME='mysql2' (1) $ oc rsync /tmp/db_archive_dir new_dbpod1234:/var/lib/mysql/data $ oc rsh new_dbpod1234
1 | mysql is the default. In this example, mysql2 is created. |
Use the appropriate commands to restore the database in the new database container from the copied database archive directory:
$ cd /var/lib/mysql/data/db_archive_dir $ mysql -u root $ source all.sql $ GRANT ALL PRIVILEGES ON <dbname>.* TO '<your username>'@'localhost'; FLUSH PRIVILEGES; $ cd ../; rm -rf /var/lib/mysql/data/db_backup_dir
You now have two MySQL database pods running in your project with the archived database.
The oc rsync
command uses the local rsync
command if present on the client’s
machine. This requires that the remote container also have the rsync
command.
If rsync
is not found locally or in the remote container, then a tar archive
will be created locally and sent to the container where tar
will be used to
extract the files. If tar
is not available in the remote container, then the
copy will fail.
The tar
copy method does not provide the same functionality as rsync
. For
example, rsync
creates the destination directory if it does not exist and will
only send files that are different between the source and the destination.
In Windows, the |
The source argument of the oc rsync
command must point to either a local
directory or a pod directory. Individual files are not currently supported.
When specifying a pod directory the directory name must be prefixed with the pod name:
<pod name>:<dir>
Just as with UNIX rsync
, if the directory name ends in a path separator (/
),
only the contents of the directory are copied to the destination. Otherwise, the
directory itself is copied to the destination with all its contents.