-
Notifications
You must be signed in to change notification settings - Fork 29
Openpgp invalid data #169
Comments
Related with that, I've renamed the |
@AntonioMeireles any idea what could be wrong with Openpgp there? Without looking to logs I cannot tell why your iTerm2 crashes. |
Which logs do you want? I can share the crash report that popup when Iterm2 starts or whatever logfile you want. |
the crash report that popup when Iterm2 starts ones, please can you try to install Openpgp and see if that helps? |
in fact, I don't have Openpgp installed :-? Here you can see the crash report of the Iterm2 when I try to set the 'initial-setup of the kube-solo VM'
|
ok, that's the iTerm crash log, no idea why that app crashes. |
When I press the Iterm crashes so I can't see anything else. The version I have is Build 3.0.15 |
|
So? What do you recommend? should I pass some parameter to that shell script in order to try it? or may be I should reinstall |
try to reboot your Mac. |
Hi.
After that, it seems that something is broken with corectl-app because no core-OS VM is running and also is impossible to download it - |
ok, I see, the brew stuff is not mine, so I cannot comment what is wrong with the install. then let me know, thanks |
I verified that the versions of the applications that brew are installed are exactly the same as you have released.
Again the problem with |
uninstall openpgp and try https://gpgtools.org/ |
As I said before, I don't have openpgp installed I have already have GPGTools installed |
GPGTools work just fine for me. |
oh! It seems that finally I found the problem! Don't know why but the command
So, I supose that happens exactly the same problem with the Btw, finally, what kind of variables (and path) do we need in order to use Best, |
kube-solo menu has an option |
Hi devs!
I'm trying to figure out why kube-solo is not working and I've found that after trying it seems that the HD was not created. I've tried to created and I've received an error about openpgp. Here you can see the details:
And here you can see the content of the logfile:
What can I do in order to start the VM and start working with kubernetes via kube-solo?
Best,
The text was updated successfully, but these errors were encountered: