WSL2 SSH config permission denied error

[sim4life]

Describe the bug
For package management and settings, I used Nix home-manager. I setup daytona with proper configs and the workspace but on opening a workspace, it gives a ssh config file permission denied error.

To Reproduce
Steps to reproduce the behavior:

1. Setup daytona git-provider with gitea (forgejo v7 self-hosted)
2. Setup daytona provider as docker-local
3. Setup daytona target as docker-local (previously added)
4. Create workspace: daytona create and select sample project: sample-astro-tailwind-restaurant gives warnings like:

1 warning found (use docker --debug to expand):
 sample-astro-tail... |  - InvalidDefaultArgInFrom: Default value for ARG $BASE_IMAGE results in empty or invalid base image name (line 4)

5. The workspace gets created but daytona is unable to open the workspace and gives the error:
   FATA[1333] open /home/myuser/.ssh/config: permission denied

Expected behaviour
Expectation is to have NO docker related warnings, NO permission errors to have read access to ssh config file and NO write access to SSH config file needed.

Desktop (please complete the following information):

• OS: (Win11 + WSL2) Ubuntu 22.04
• Docker desktop (using WSL2 bindings) v4.37.1
• Nix home-manager v24.05
• Daytona Version: v0.50.0

Additional context

1. myuser is the WSL2 Ubuntu user with sudo privileges.
2. I don't have VS Code installed but I use VSCodium. Whether, I select VS Code or Terminal SSH in the default daytona ide, I get the same ssh config permission denied error.
3. Using Nix home-manager to manage SSH settings, it creates a chain of symlinks to another file inside Nix directory
   lrwxrwxrwx 1 myuser myuser /home/myuser/.ssh/config -> /nix/store/xyzhash-home-manager-files/.ssh/config
lrwxrwxrwx 2 root root /nix/store/xyzhash-home-manager-files/.ssh/config -> /nix/store/abchash-hm_.sshconfig
-r--r--r-- 3 root root /nix/store/abchash-hm_.sshconfig

[Tpuljak]

@sim4life thanks for opening the issue.

The reason that daytona needs write permissions to your ssh config is to setup the necessary SSH host to connect to the Daytona workspace.

We first add Include daytona_config into the ssh config and then create the daytona_config file in which we write Hosts similar to this:

Host default-078a65b78fb5-tpuljak
	User daytona
	StrictHostKeyChecking no
	UserKnownHostsFile /dev/null
	ProxyCommand "/usr/local/bin/daytona" ssh-proxy default 078a65b78fb5 tpuljak
	ForwardAgent yes

Looking at your symlink, the issue might be that the nix-created ssh config is not writable by your user (without sudo).

Are you able to run echo test >> ~/.ssh/config without sudo?

P.S. Sorry for the late response, we were on holidays

[sim4life]

@Tpuljak welcome back.
Yes, you're right. I can NOT write to my ~/.ssh/config without sudo.

Is there a way for me to have the daytona generated ssh config specific for my user so that I can put it manually in my nix home-manager managed ssh config file?
Afterwards, will it be possible for daytona to verify the correct ssh config even if it does NOT get the write access to my ssh config file?

[Tpuljak]

@sim4life currently, we have the ssh config file hardcoded.

We could add an option to skip writing the Include daytona_config line in ~/.ssh/config and only write the daytona hosts in ~/.ssh/daytona_config. You would then be responsible for adding the Include line yourself.

Just to give it a try, can you please add Include daytona_config to the top of your config file manually and then try to open the workspace with daytona code?

[sim4life]

I added the Include daytona_config directive in my ~/.ssh/config but daytona code still gave the same permission denied error.
Keep in mind that the ~/.ssh/daytona_config file was auto-generated during previous steps but it is an empty file with only rw permissions for the myuser
-rw------- 1 myuser myuser daytona_config

[Tpuljak]

I added the Include daytona_config directive in my ~/.ssh/config but daytona code still gave the same permission denied error.

Ah, I see now that we run the replace every time. Because we need to ensure that the Include line is on top of the file, we inject it on every run.

[Tpuljak]

We'll release an update for this today and then you can check again.

[Tpuljak]

@sim4life forgot to update you. You can update to the latest version of daytona by rerunning the install script. The issue should be resolved. Let me know if it works now.