Run command in actual container to backup

[smurfy]

Currently as far as i gathered from the code, the DUMP commands start a separate container and then execute commands in it.

What i need and which possible can fix / workaround #26 would be the ability to run actual commands in the "tagged/labeled" container.

For example i have an ejabberd container. With a command, i could dump the database somewhere, set the correct permissions to the dump file and add the file to /backup of rancher-backup.

I could also run a rsync or something of other data to /backup without actually mounting the data themself. (to fix the permission problem)

[disaster37]

It's fix on webcenter/rancher-backup:develop. Read #26 comment for more detail.

[smurfy]

Well not really, while the permission problem is fixed, the other benefit of a way to do docker exec on the actual container for dumping still exist.

As a mentioned before i have a ejabberd container where remote backup (like with databases) is not really possible. So i need to run a command:

docker exec CONTAINER ejabberdctl backup /opt/ejabberd/backup/ejabberd.backup

to do the backup, instead of creating a dump container

Hope you understand what i mean :)

[disaster37]

I doesn't know ejabberd, but there are a problem with docker exec command. To do work, the backup container will be run on same host of your ejabber container...

Maybee another way is to add same some tools on your ejabber image like gocron to perform backup each hours or days on distributed storage. And them mount the same distributed storage on backup container ?

[smurfy]

Ok thank you, i run everything on the same host, so i never thought about docker exec can be a problem. But whats about rancher-cli?

http://rancher.com/docs/rancher/v1.6/en/cli/commands/#rancher-exec-reference

But since ejabberd supports mysql as backend, i probably will migrate, so i can use the default mysql dump.