---
# System prepended metadata

title: SSH Into Session

---

# SSH Into Session

### Notes on CLI
- [x] :beetle: BUG: double `repo/repo` in remote URL
- [x] No feedback upon running `renku session ssh-setup` that it worked
- [ ] I run `ssh-setup`, then run `renku session start --ssh`, and it says `Your system is not set up for SSH connections to Renku. Would you like to set it up? [y/N]:` - Confusing!!
    - [ ] -> `ssh-setup` not needed anymore! Remove `ssh-setup` from docs
- [X] I think it's worth making the SSH workflow not require Docker. The workflow currently adds the SSH key, then immediately prompts that the image isn't build for the commit with the keys. What can we do here for users without Docker? (Give option to wait for image to build? Can we get feedback here on the status of the image build?)

TESTING NOTES: 
- manually added SSH entry to template

### Notes on VSCode

- It's a little ugly to see the jumphost in the remote ssh targets list - is there any (easy) way to prevent that from happening? I guess one option would be to just include the jumphost config in each config - is that so bad?


### Notes on Docs
- Verb headings ("How to...")
- lists over paragraphs whenever possible


### Sync 17 Feb 2023
**Need to Haves for release on 28 Feb**
- [x] RG: When you `renku session open` and ssh in, you don't land in your project directory
- [ ] Docs
    - [x] RG: something about changes in Dockerfile not taking effect
    - [x] RG: forcing a template to be ssh supported
    - [x] RG: Move note about adding SSH to custom templates for template maintainers to template docs
    - [X] LKK: Add note that to use password protected keys, use -k option
    - [X] LKK: ref links to ssh commands
        - [ ] How link to `renku session x` subcommands?
    - [X] LKK: note normal ssh command (not renku session open)
- [ ] YAT: prep/configure for the release roll-outs after this next Renku Meeting
    - [ ] Dev - ?
    - [ ] Limited - 1 March
    - [ ] RenkuLab - 6 March
    - [ ] UnLimited (Azure) - ?

Start with options
Start SSH session

**Nice to Haves**
- [x] `renku session start` shows next commands to use?
    - nevermind- prints normal `ssh` command, just kind of buried two lines up...
- [ ] [Not in scope for this build, but note for the future] When only have 1 running session, don't need to specify id for `renku session open/stop`



### Sync 8 Feb 2023
What’s left (of need-to-haves)?
Back end
- [x] update templates
- [x] garbage collection on expired session ssh hosts (so don’t get ever increasing list)
- [x] renku session open
- [x] (nice to have) combine ssh-setup with first session start
- [x] Documentation
    - [Docs PR](https://github.com/SwissDataScienceCenter/renku/pull/2947/files)

Front end
- [ ] Lorenzo’s Issues…. (feel free to loop in Laura for writing user-facing text)

Ops
- [x] Ralf to talk to YAT about implementing port stuff, preferably at least on:
  * Dev
  * Limited
  * RenkuLab