podman-remote cp fails with error "you must use just one container"

[sshnaidm]

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description
When running podman-remote cp it fails with error you must use just one container

Steps to reproduce the issue:

podman-remote --username fedora --remote-host 192.168.2.5 cp /tmp/file1 cont44:/tmp/file1
Error: invalid arguments /tmp/file1, cont44:/tmp/file1 you must use just one container

While container cont44 exists on remote:

podman-remote --username fedora --remote-host 192.168.2.5 ps
CONTAINER ID  IMAGE                              COMMAND     CREATED       STATUS           PORTS  NAMES
35a3948defce  docker.io/library/python:3-alpine  sleep 100d  15 hours ago  Up 15 hours ago         cont44

podman-remote --username fedora --remote-host 192.168.2.5 exec -it cont44 ls /tmp/
...

Describe the results you received:
Error "you must use just one container" and file is not copied

Describe the results you expected:
File is copied from local machine to remote container

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

Version:            1.5.1
RemoteAPI Version:  1
Go Version:         go1.12.7
OS/Arch:            linux/amd64

Output of podman info --debug:

debug:
  compiler: gc
  git commit: ""
  go version: go1.12.7
  podman version: 1.5.1
host:
  BuildahVersion: 1.10.1
  Conmon:
    package: podman-1.5.1-3.fc30.x86_64
    path: /usr/libexec/podman/conmon
    version: 'conmon version 2.0.0, commit: d728afa06cd2df86a27f32a4692c7099a56acc97-dirty'
  Distribution:
    distribution: fedora
    version: "30"
  MemFree: 800608256
  MemTotal: 25141854208
  OCIRuntime:
    package: runc-1.0.0-93.dev.gitb9b6cc6.fc30.x86_64
    path: /usr/bin/runc
    version: |-
      runc version 1.0.0-rc8+dev
      commit: e3b4c1108f7d1bf0d09ab612ea09927d9b59b4e3
      spec: 1.0.1-dev
  SwapFree: 3497410560
  SwapTotal: 12645822464
  arch: amd64
  cpus: 4
  eventlogger: journald
  hostname: sshnaidm.remote
  kernel: 5.2.15-200.fc30.x86_64
  os: linux
  rootless: true
  uptime: 306h 16m 32.79s (Approximately 12.75 days)
registries:
  blocked: null
  insecure: null
  search:
  - docker.io
  - registry.fedoraproject.org
  - quay.io
  - registry.access.redhat.com
  - registry.centos.org
store:
  ConfigFile: /home/sshnaidm/.config/containers/storage.conf
  ContainerStore:
    number: 16
  GraphDriverName: overlay
  GraphOptions:
  - overlay.mount_program=/usr/bin/fuse-overlayfs
  GraphRoot: /home/sshnaidm/.local/share/containers/storage
  GraphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  ImageStore:
    number: 17
  RunRoot: /tmp/1000
  VolumePath: /home/sshnaidm/.local/share/containers/storage/volumes

Package info (e.g. output of rpm -q podman or apt list podman):

podman-1.5.1-3.fc30.x86_64

Additional environment details (AWS, VirtualBox, physical, etc.):

[sshnaidm]

Closing it because podman-remote cp isn't implemented yet, see #4203

[rhatdan]

Please open an issue on adding this support if the issue does not currently exists.

[sshnaidm]

@rhatdan opened #4207

[rhatdan]

Thanks.