-
Notifications
You must be signed in to change notification settings - Fork 94
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
Finch vm init failed after install #38
Comments
I looked up similar issue and seems rancher rke also had this issue before: rancher/rke#2696 However in the current case, lima did finish booting the vm because it shows vm started successfully, but it still shows the fatal error. @Zlender could you please try |
I'm seeing the same error. It's reproducible with
|
With
|
@KevinLiAWS this is the output
|
|
Thanks for your detailed debug info. @Zlender and @oraclesean could you please share me your mac os version? I noticed that it might be related with the mac os version, so I would like to collect more data about the env. Thanks |
Sure
|
Same issue. $ uname -v
Darwin Kernel Version 21.6.0: Thu Sep 29 20:13:56 PDT 2022; root:xnu-8020.240.7~1/RELEASE_ARM64_T6000
$ sw_vers
ProductName: macOS
ProductVersion: 12.6.1
BuildVersion: 21G217 |
|
same issue here $ uname -v
Darwin Kernel Version 21.6.0: Thu Sep 29 20:13:56 PDT 2022; root:xnu-8020.240.7~1/RELEASE_ARM64_T6000
$ sw_vers
ProductName: macOS
ProductVersion: 12.6.1
BuildVersion: 21G217 |
Same issue.
|
Signed-off-by: Justin Alvarez <alvajus@amazon.com> Issue #, if available: Fixes #103. Still having trouble reproducing #38, but possibly related *Description of changes:* - Our Lima configuration (finch.yaml) was using the default value for the `ssh.loadDotSSHPubKeys` option, which is `true`. This may cause errors if the user has any issues with the keys in their `.ssh` directory. Since the correct key is generated and stored in Lima's directories, and the user is not expected to interact directly with the VM anyway, we can just set this to `false` explicitly - In the future, we can consider adding this to finch's config (probably by adding logic to `pkg/config`'s `lima_config_applier` and `defaults.go`) *Testing done:* - Reproduced the error by creating an invalid pub key entry. Made the change to my local `lima.yaml` and rebooted the vm, and did not see the error - [x] I've reviewed the guidance in CONTRIBUTING.md #### License Acceptance By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. Signed-off-by: Justin Alvarez <alvajus@amazon.com>
Signed-off-by: Justin Alvarez <alvajus@amazon.com> Issue #, if available: Fixes runfinch#103. Still having trouble reproducing runfinch#38, but possibly related *Description of changes:* - Our Lima configuration (finch.yaml) was using the default value for the `ssh.loadDotSSHPubKeys` option, which is `true`. This may cause errors if the user has any issues with the keys in their `.ssh` directory. Since the correct key is generated and stored in Lima's directories, and the user is not expected to interact directly with the VM anyway, we can just set this to `false` explicitly - In the future, we can consider adding this to finch's config (probably by adding logic to `pkg/config`'s `lima_config_applier` and `defaults.go`) *Testing done:* - Reproduced the error by creating an invalid pub key entry. Made the change to my local `lima.yaml` and rebooted the vm, and did not see the error - [x] I've reviewed the guidance in CONTRIBUTING.md #### License Acceptance By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. Signed-off-by: Justin Alvarez <alvajus@amazon.com>
After v0.2.0 released, the issue looks like not resolved
|
Also running into this problem.
|
Did some research and found similar issue here: https://support.okta.com/help/s/article/No-supported-methods-remain-unable-to-ssh-to-target-server-via-sft?language=en_US |
Closing the issue because of no response. Feel free to reopen. |
Describe the bug
Using Finch Finch-v0.1.0-aarch64 the command vm init fails with fatal error as seen in the logs section.
It the end it looks like
init
did succeed as I can build and run containers.Steps to reproduce
Install Finch-v0.1.0-aarch64 and run
finch vm init
Expected behavior
No fatal error.
Screenshots or logs
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: