-
Notifications
You must be signed in to change notification settings - Fork 647
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
Command to exit the ssh session #3125
Comments
There is another command called check, which will print the current status: $ ssh -F $(limactl ls --format='{{.SSHConfigFile}}' docker) lima-docker -O check
Master running (pid=425902) This process doesn't seem to be recorded anywhere else, i.e. there is no ssh.pid But it's not too hard to find it: |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I fear how this affects reverse-sshfs mounts (as well as port forwards) |
There are known workarounds for the issues, like sourcing the profile again or starting a new shell with The brute force approach is to do a |
@afbjorklund Hi! I want to work on this issue and I've been able to reproduce it. I'm considering adding a new command, something like |
Having a |
I have implemented a |
Description
By default, the ssh connection to the lima instance is kept open between commands. (the
ssh.sock
)But this also means that you don't get a new session, if environment changes or any groups are added.
So if you change the prompt or if you add a docker group, it is not reflected in the ongoing shell.
Historically I just deleted the socket, but it could be nice with a
limactl shell
option to exit nicely?Then the next login will be "fresh" again.
EDIT: There is a function in sshocker do to it, called ssh.ExitMaster
For lima, we might want to restart it again as part of the hostagent?
And to re-establish the reverse-sshfs mounts (if any), and so on (ports).
This could also be useful in other places, like after resume from sleep:
The text was updated successfully, but these errors were encountered: