-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
3.26.0.GA
-
False
-
-
False
-
Release Notes
-
Known Issue
-
Proposed
-
Workaround Exists
-
Description of problem:
While following the official DevSpaces documentation to connect to a running workspace via Remote SSH, the documented SSH configuration fails on macOS when the IdentityFile path uses $HOME.
Replacing $HOME with ~ allows the Remote SSH connection to work successfully.
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
- Ensure workspace is running (example: empty-ipwg-onta).
- Login to the OpenShift cluster:
- Run port-forward
- Configure SSH client on macOS using the documented steps
This can also be configured locally in the client SSH configuration file (eg. $HOME/.ssh/config) with the following :
Host localhost HostName 127.0.0.1 User user Port 2022 IdentityFile $HOME/.ssh/ssh_client_ed25519_key UserKnownHostsFile /dev/null
5 Attempt to connect using VS Code → Remote SSH.
Actual results:
- Remote SSH fails to start.
- Connection does not establish when $HOME is used in IdentityFile.
- No clear error indicating path resolution failure.
Expected results:
- $HOME should be correctly resolved as ~ on macOS, as documented.
- Remote SSH should connect successfully using the documented configuration.
Reproducibility (Always/Intermittent/Only Once):
Acceptance criteria:
Definition of Done:
Build Details:
Additional info (Such as Logs, Screenshots, etc):