SSH keys are available to all containers only after workspace reboot

Describe the bug

After using the >SSH generate key-pair command, the keypair is generated in the theia-ide container only, not accessible for the other running containers.

By default the terminal can be only opened for the deployment container.

It can be circumvented by showing the tool containers or running a new terminal from My Workspace->Plugins->theia-ide

However, after the reboot the key is available in /etc/ssh and the checkout works from all containers.

I would suggest instead of storing the key into /home/theia/.ssh to store it straight into /etc/ssh and restarting the sshd daemon @vparfonov

Che version

• latest
• nightly
• other: please specify (hosted che @ che.prod-preview.OSIO) 7.0.0-rc-4.0

Expected behavior

The git clone should be possible from any container right after the key has been generated and added into your git service of choice

Runtime

• kubernetes (include output of kubectl version)
• Openshift (include output of oc version)
• minikube (include output of minikube version and kubectl version)
• minishift (include output of minishift version and oc version)
• docker-desktop + K8S (include output of docker version and kubectl version)
• other: (please specify)

OpenShift Master: v3.11.82 Kubernetes Master: v1.11.0+d4cacc0 OpenShift Web Console: v3.11.82

Installation method

• chectl
• che-operator
• minishift-addon
• I don’t know

Environment

• my computer
  • Windows
  • Linux
  • macOS
• Cloud
  • Amazon
  • Azure
  • GCE
  • other (please specify)
• other: please specify

[vinokurig]

@sunix

@vparfonov @vinokurig @l0rd why don’t we write to it : we mount it we can have write access.

wright access will not solve the problem, It doesn’t matter where the keys are located after generation, in /etc/ssh or in ~/.ssh. The problem is that the key file is generated only for theia-ide container.

[vinokurig]

It is not possible to store keys in the /etc/ssh after generating a key, there is no wright access.