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"
2

+1 We have same issue

3

@hoangdox I fixed this by creating SSH Certificate Authority and Certificate Authority in press…(Also remember to mention the certificate authority in press settings and in proxy server)

image

image
image752×114 21.5 KB

4

Can send me step create or video? input field when create?

1 Like
5
  1. create ssh ca
  2. enable developer mode and create root ca
  3. add ssh ca in SSH Certificate Authority in proxy server settings
  4. save settings and trying to “setup ssh proxy”

got same error…

…After 2 days of investigations )) finaly: on the page of created SSH Certificate Authority press “Actions > Build Image” and after that playbook “Setup SSH Proxy” will end with success state!