Struggling with --sync when starting notebook (from Windows WSL2)

[rsignell]

I'm struggling with --sync when starting a Coiled notebook from Windows WSL2:

How can I fix that ssh issue. I do have ssh in WSL:

(base) $ which ssh
/usr/bin/ssh

[rsignell]

Oh! I just tried installing openssh into my conda environment:

mamba install openssh

(base) $ which ssh
/home/rsignell/miniforge3/bin/ssh

and now I don't get the sync error!

[rsignell]

Hmm, actually I do still get that error with openssh:

(base) rsignell@OSC:~/repos/unige-pangeo-course$ coiled notebook start --region us-east-1 --vm-type m5.xlarge --sync --s
oftware pangeo --name pangeo --workspace pangeo --disk-size 200GB
Launching file synchronization...
╭───────────────────────────── Notebook pangeo... ─────────────────────────────╮
│                                                                              │
│ Jupyter:                                                                     │
│ https://cluster-onozh.dask.host/jupyter/lab/tree/synced?token=n82JRxY9naAVkJ │
Error attempting to ssh...

Warning: Permanently added 'cluster-onozh.dask.host' (ED25519) to the list of
known hosts.
[email protected]: Permission denied (publickey).

[ntabris]

Hi, @rsignell. We're trying to figure out how to make notebook sync (or something that covers the same need) more reliable, but in the mean time, would you be able to try restarting and see if it works for you after that? It seems like a restart helps many people who have this issue.

[rsignell]

Rebooted. But unfortunately it still had the same error.