Support `cp' sub command

[arnisoph]

For now, docker-compose cp is missing. :)

$ docker-compose -v
docker-compose version 1.7.1, build 0a9ab35

$ docker-compose -h
Define and run multi-container applications with Docker.

Usage:
  docker-compose [-f <arg>...] [options] [COMMAND] [ARGS...]
  docker-compose -h|--help

Options:
  -f, --file FILE             Specify an alternate compose file (default: docker-compose.yml)
  -p, --project-name NAME     Specify an alternate project name (default: directory name)
  --verbose                   Show more output
  -v, --version               Print version and exit
  -H, --host HOST             Daemon socket to connect to

  --tls                       Use TLS; implied by --tlsverify
  --tlscacert CA_PATH         Trust certs signed only by this CA
  --tlscert CLIENT_CERT_PATH  Path to TLS certificate file
  --tlskey TLS_KEY_PATH       Path to TLS key file
  --tlsverify                 Use TLS and verify the remote
  --skip-hostname-check       Don't check the daemon's hostname against the name specified
                              in the client certificate (for example if your docker host
                              is an IP address)

Commands:
  build              Build or rebuild services
  config             Validate and view the compose file
  create             Create services
  down               Stop and remove containers, networks, images, and volumes
  events             Receive real time events from containers
  exec               Execute a command in a running container
  help               Get help on a command
  kill               Kill containers
  logs               View output from containers
  pause              Pause services
  port               Print the public port for a port binding
  ps                 List containers
  pull               Pulls service images
  restart            Restart services
  rm                 Remove stopped containers
  run                Run a one-off command
  scale              Set number of containers for a service
  start              Start services
  stop               Stop services
  unpause            Unpause services
  up                 Create and start containers
  version            Show the Docker-Compose version information

[ocramz]

@bechtoldt What should cp do?

[ain]

docker-compose cp <container> <path> <local path>, e.g.

$ docker-compose cp db /var/lib/postgresql ~/Downloads/database_backup

[arnisoph]

@ocramz ^

[ain]

@bechtoldt @ocramz I also filed #3609 earlier, would offer great value when working with data across containers.

[ColinHebert]

That would be an awesome feature.

On top of that a support of copy in the configuration file (#1664) would be perfect

+1 for this feature. need copy some files into running container

[dorgan]

+1.... having to build a container to get a large file or 2 updates is a pain.

[alberto56]

As a workaround, you can do:

docker cp /path/to/my-local-file.sql "$(docker-compose ps -q mycontainer)":/file-on-container.sql

Now /file-on-container.sql will exist on your running container:

docker-compose exec mycontainer /bin/bash -c 'ls -lah /file-on-container.sql'
-rw-r--r-- 1 root root 244M Nov 14 19:48 /file-on-container.sql

[harobed]

I use this bash alias:

alias docker-compose-cp="function _f(){ docker cp \$2 \`docker-compose ps -q \$1\`:\$3;};_f"

:)

[johnmarcou]

With a "files" option in Compose which can copy local file to remote container between creation and starting process, it could be amazing to inject config files and secrets 👍

With local docker daemon, you can use "volumes" to map local file in a container, but it is not possible with remote docker daemon.

version: '2'
services:
  service1:
    image: nginx
    files:
      - nginx.conf:/etc/nginx/conf.d/nginx.conf
      - cert.crt:/etc/nginx/certs/cert.crt

[johanbrandhorst]

The workarounds suggested here are not bad, but the prime reason to want this is so that the cp is guaranteed to be executed before the command, which like @johnmarcou points out allows docker-compose to interact much better with remote docker daemons (i.e. ANY cloud based CI service). This should be a high priority feature imo.

[bperel]

Wouldn't it make more sense to use the service name rather than the container name ?
docker-compose cp [OPTIONS] SERVICE SRC_PATH DEST_PATH

So that we're in sync with the syntax of docker-compose exec which is:

$ docker-compose exec
Execute a command in a running container

Usage: exec [options] SERVICE COMMAND [ARGS...]

[ilinum]

How would it work if there are multiple instances of the same service?
If there are multiple containers, which one should it copy to?

[keithmattix]

Was there any resolution to this? I think this would be a very nice feature!