Cannot connect to containers due to pre-existing settings in ~/.ssh/config

[richard-fairthorne]

Cannot connect to containers due to pre-existing settings in ~/.ssh/config

[richard-fairthorne]

User workarounds:

• change the config order after creating the container
• remove any settings that override devpod settings
• do not use a 'Host *' section for default SSH settings

I am not a project maintainer, but this seems like a good first issue for a developer who is new to the project, as the problem is clearly defined, and the solution is not overly-complex.

[pascalbreuninger]

Hey @richard-fairthorne, that's a fair point. We append it to the SSH file to minimize the possibility of messing anything up, prepending would be very prone to unexpected side effects if you're not aware DevPod is changing your ~/.ssh/config file.

However, you can point DevPod to a separate file that's being used for ssh configuration, either by setting it in the context for all workspaces devpod context set-options -o SSH_CONFIG_PATH=./your_file or individually per workspace devpod up --ssh-config=./your_file

[richard-fairthorne]

I appreciate the response.

As far as I have seen, all devpod settings are specific to exactly one host. I may be missing something, but I don't see how options for individual hosts would mess up global settings, or settings for other hosts.

This is a fantastic product, and as a brand new user with no orientation to the product, this was the thing that nearly made me hit "uninstall". I'm glad I persisted. While I've gotten over this hurdle with simple workarounds, as a new user, I couldn't use the product without debugging this problem first.

My initial impression was that the product simply doesn't work.

I understand being cautious about messing up people's config file, but I hope you reconsider the placement of the host configurations.