Skip to content

Stop using hard-coded port 60022 for "default" instance #3780

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

AkihiroSuda
Copy link
Member

@AkihiroSuda AkihiroSuda commented Jul 31, 2025

The "default" instance no longer uses 60022 as the SSH port.

Discussed in:

This change affects the existing "default" instance too, however, users do not need to care about the port number if they use ~/.lima/default/ssh.config:

ssh -F ~/.lima/default/ssh.config lima-default

@msimkunas
Copy link

msimkunas commented Aug 1, 2025

Just wanted to note that users do care about ports in certain cases. For example, Jetbrains IDEs require you to specify the port manually even if you use the lima-* host alias to connect to the VM.

In such cases, the user will want to reserve a host port for exclusive VM use via ssh.localPort in the template.

The "default" instance no longer uses 60022 as the TCP port.

Discussed in issue 3712.

This change does not affect the existing "default" instance.

Users do not need to care about the port number
if they use `~/.lima/default/ssh.config`:
```
ssh -F ~/.lima/default/ssh.config lima-default
```

Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
@AkihiroSuda AkihiroSuda force-pushed the remove-hardcoded-60022 branch from 06b2ff0 to d5b3fc2 Compare August 4, 2025 08:46
@AkihiroSuda
Copy link
Member Author

In such cases, the user will want to reserve a host port for exclusive VM use via ssh.localPort in the template.

Added --ssh-port flag for convenience:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants