Skip to content

READY. Run ... to open the shell is confusing when the shell is already launched. #3452

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
AkihiroSuda opened this issue Apr 21, 2025 · 0 comments
Labels
area/cli limactl CLI user experience bug Something isn't working good first issue Good for newcomers

Comments

@AkihiroSuda
Copy link
Member

$ lima
? Do you want to start the instance now?  Yes
INFO[0000] Starting the instance "default" with VM driver "vz" 
INFO[0000] [hostagent] hostagent socket created at /Users/suda/.lima/default/ha.sock 
INFO[0000] [hostagent] Starting VZ (hint: to watch the boot progress, see "/Users/suda/.lima/default/serial*.log") 
INFO[0001] SSH Local Port: 60022                        
INFO[0001] [hostagent] [VZ] - vm state change: running  
INFO[0001] [hostagent] Waiting for the essential requirement 1 of 2: "ssh" 
INFO[0011] [hostagent] Waiting for the essential requirement 1 of 2: "ssh" 
INFO[0011] [hostagent] The essential requirement 1 of 2 is satisfied 
INFO[0011] [hostagent] Waiting for the essential requirement 2 of 2: "user session is ready for ssh" 
INFO[0011] [hostagent] The essential requirement 2 of 2 is satisfied 
INFO[0011] [hostagent] Waiting for the optional requirement 1 of 2: "systemd must be available" 
INFO[0011] [hostagent] Guest agent is running           
INFO[0011] [hostagent] The optional requirement 1 of 2 is satisfied 
INFO[0011] [hostagent] Forwarding TCP from 127.0.0.1:44273 to 127.0.0.1:44273 
INFO[0011] [hostagent] Waiting for the optional requirement 2 of 2: "containerd binaries to be installed" 
INFO[0011] [hostagent] Not forwarding TCP 127.0.0.53:53 
INFO[0011] [hostagent] Not forwarding TCP 127.0.0.54:53 
INFO[0011] [hostagent] Not forwarding TCP 0.0.0.0:22    
INFO[0011] [hostagent] Not forwarding TCP [::]:22       
INFO[0011] [hostagent] Not forwarding UDP 127.0.0.54:53 
INFO[0011] [hostagent] Not forwarding UDP 127.0.0.53:53 
INFO[0011] [hostagent] The optional requirement 2 of 2 is satisfied 
INFO[0011] [hostagent] Not forwarding UDP 192.168.5.15:68 
INFO[0011] [hostagent] Waiting for the guest agent to be running 
INFO[0011] [hostagent] Waiting for the final requirement 1 of 1: "boot scripts must have finished" 
INFO[0011] [hostagent] The final requirement 1 of 1 is satisfied 
INFO[0011] READY. Run `lima` to open the shell.         
suda@lima-default:/Users/suda$ lima
Command 'lima' not found, did you mean:
  command 'limo' from snap limo (0.0.4.20230109)
  command 'lzma' from deb xz-utils (5.6.2-2)
  command 'lzma' from deb lzma (9.22-2.2)
See 'snap info <snapname>' for additional versions.

"Run lima to open the shell(or "Runlimactl shell INSTto open the shell") should not be printed when the shell is already launched. This happens when an instance is started vialima (limactl shell`)

@AkihiroSuda AkihiroSuda added area/cli limactl CLI user experience bug Something isn't working good first issue Good for newcomers labels Apr 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cli limactl CLI user experience bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant