-
Notifications
You must be signed in to change notification settings - Fork 0
An offline workspace with a file sync session is accessed using coder ssh
if config-ssh
was run
#590
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Comments
|
Or let us make |
That's what's accomplished by the second option above, creating an option on Mutagen to specify the SSH config to use. |
ethanndickson
added a commit
to coder/mutagen
that referenced
this issue
May 1, 2025
…ble (#4) Relates to coder/internal#590 I've tested this manually, and within Coder Desktop macOS, by setting `MUTAGEN_SSH_CONFIG_PATH` to `none`. From the man page for `ssh(1)`: ``` -F configfile [...] If set to “none”, no configuration files will be read. ``` Subsequent PRs for the Desktop apps will use the new Mutagen version (0.18.3), and specify `MUTAGEN_SSH_CONFIG_PATH=none`
ethanndickson
added a commit
to coder/coder-desktop-macos
that referenced
this issue
May 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The latest
coder config-ssh
creates an SSH config item that fallsback tocoder ssh
if the Coder Connect hostname is unavailable. This means if a file sync session exists for a workspace that's currently offline, rather than failing to connect, Mutagen uses the SSH config and attempts to connect to that workspace usingcoder ssh
, this in-turn automatically starts the workspace, and then when the Mutagen operation times out, cancels the build.These are the Mutagen logs relayed via the Coder Desktop logs:
One way to fix this might be to patch our Mutagen build to ignore the SSH config. This should be fine as nobody should ever need or want to customize the SSH config used by the file sync connection.
This was observed on Mac, but presumably occurs on Windows too.
The text was updated successfully, but these errors were encountered: