lorri
lorri copied to clipboard
Use sqlite
- [ ] Amended the changelog in
release.nix
(seerelease.nix
for instructions)
@mwoodpatrick: thanks for reporting, I'll try to replicate the issue and keep you in the loop.
@mwoodpatrick: sorry for the delay, testing it now. Just to be sure, the report mentions GitHub, but the error has GitLab written in it. I will test both, but I want to be sure of what you tried when you get this error.
@mwoodpatrick: so I wasn't able to replicate the issue with GitHub, but I will try GitLab now.
I am using GitHub, any suggestions on the best way for me to debug this further so I can get some insight on where the error is happening?
Does this error happen again if you retry the same command?
If so, can you show me the output of kubectl get pods -A
please.
Also, I don't think we change anything in k3d, but you can also try with the latest version 2.4.8
which is the one I used. I'm trying it one last time on another Linux system just to be sure.
So I did a clean install with 2.4.8 and this time I got the error:
Error: unable to reach vault over https - this is likely due to the mkcert certificate store missing. please install it via /home/mwoodpatrick/.k1/kubefirst/tools/mkcert -install
Is this expected?
Also using this using this version I'm still seeing the other issue I reported a day or so ago:
Running kubefirst changes my stty settings #2176
Is this expected?
Yes, you need to install this. You can find more information about this needed installation step at https://docs.kubefirst.io/k3d/quick-start/install#install-the-ca-certificate-authority-of-mkcert-in-your-trusted-store
lso using this using this version I'm still seeing the other issue I reported a day or so ago
It make sense as we didn't tackle this bug yet, but the team has been notified and I was able to reproduce.
I'm running on "Debian GNU/Linux 12 (bookworm)" so I don't have brew but installed mkcert using:
sudo apt install mkcert libnss3-tools
mkcert -install
Including the additional steps for Windows with WSL
This was completed without issue and I was able to get further running:
kubefirst k3d create
This did install the k3d clusters and argo but did hit some issues see log
Log shows:
Hit error Unsupported attribute
Running:
/home/mwoodpatrick/.k1/kubefirst/tools/terraform validate
reports:
Success! The configuration is valid.
I found my problem (I forgot to export my GITHUB_TOKEN), it would be good if the command checked to see if it was set.
It is supposed to detect it, and still working on macOS. Let me try on WSL2 with Debian.
I tried on Debian, and it is showing the following screen when I didn't have the environment variable set.
So since you were able to crate a cluster properly, and I cannot reproduce the token one, I'll close this issue.
If you encounter the same issue about the token in the future, create a new issue so it will be easier to follow as this one was about multiple things.