Fixing Docker 'cp' Misinterpretation in SSH Proxy Setup

Frappe Cloud
, , , ,
1

I’m trying to set up an SSH proxy using Docker by following an official playbook. However, I’m encountering an issue where the cp command is being misinterpreted as the Docker image name, resulting in the following error:

Unable to find image 'cp:latest' locally
docker: Error response from daemon: pull access denied for cp, repository does not exist or may require 'docker login'.

Here’s the relevant portion of the playbook:

- name: Copy home directory from SSH Image
  become: yes
  become_user: frappe
  command: "docker run --rm --net none -v /home/frappe/ssh/home:/homemount cp -RL /home/. /homemount"