Failure for UI install command kubefirst launch up

[linear]

Instructions from here
https://kubefirst.konstruct.io/docs/civo/quick-start/install/ui

I'm on kubefirst 2.6.1
Running kubefirst launch up

Fails with the following:

kubefirst launch up


   Welcome to Kubefirst

  💡 To view verbose logs run below command in new terminal:

  tail -f -n +1 /Users/ccosta/.k1/logs/log_1729087280.log

  📘 Documentation: https://docs.kubefirst.io/

  ⏰ Estimated time: 10 minutes


  ✅ Download k3d
  💫 Create k3d cluster




stat /Users/ccosta/.k1/kubefirst-console/kubeconfig: no such file or directory
ERRO[0000] unable to locate kubeconfig file - checked path: /Users/ccosta/.k1/kubefirst-console/kubeconfig
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x105e8b380]

goroutine 12 [running]:
k8s.io/client-go/kubernetes.NewForConfig(0x10a079de0?)
	k8s.io/client-go@v11.0.1-0.20190816222228-6d55c1b1f1ca+incompatible/kubernetes/clientset.go:414 +0x20
github.com/konstructio/kubefirst-api/internal/k8s.CreateKubeConfig(0xe0?, {0x14000bf1890?, 0x3e?})
	github.com/konstructio/kubefirst-api@v0.102.0/internal/k8s/client.go:74 +0x244
github.com/konstructio/kubefirst/internal/launch.Up({0x10a0fdda0, 0x0, 0x0?}, 0x0, 0x1)
	github.com/konstructio/kubefirst/internal/launch/cmd.go:179 +0xcd0
github.com/konstructio/kubefirst/cmd.launchUp.func1(0x140001dd400?, {0x106f9bcd3?, 0x4?, 0x106f9bd8f?})
	github.com/konstructio/kubefirst/cmd/launch.go:40 +0x3c
github.com/spf13/cobra.(*Command).execute(0x1400054db08, {0x10a0fdda0, 0x0, 0x0})
	github.com/spf13/cobra@v1.7.0/command.go:944 +0x630
github.com/spf13/cobra.(*Command).ExecuteC(0x10a082e20)
	github.com/spf13/cobra@v1.7.0/command.go:1068 +0x320
github.com/spf13/cobra.(*Command).Execute(...)
	github.com/spf13/cobra@v1.7.0/command.go:992
github.com/konstructio/kubefirst/cmd.Execute()
	github.com/konstructio/kubefirst/cmd/root.go:50 +0x3c
main.main.func2()
	github.com/konstructio/kubefirst/main.go:133 +0x1c
created by main.main in goroutine 1

[linear]

KRA-19 Failure for UI install command `kubefirst launch up`

[fharper]

Before launch up again, can you ensure that delete the ~/.k1 folder, the ~/.kubefirst file, and anything k3d in Docker? If you try it again, do you still have that issue? I feel like this happens when kubefirst think there is already an existing cluster, but it's not the case, or it's remaining from the past :)

[konstructcarrie]

@fharper Thank you confirmed. Two things I think we need to address here.

1. Our deprovisioning docs don't make it clear that it leaves a lot of Kubefirst stuff behind
2. The UI install documentation assumes that you've never installed Kubefirst before and the failure of the kubefirst launch up command doesn't provide any information on why it's failing

Also I got as far as the command being successful but then I got stuck trying to open the Console

[fharper]

Our deprovisioning docs don't make it clear that it leaves a lot of Kubefirst stuff behind

It shouldn't if you follow all the steps and everything goes well which wasn't your case I think. Happy to discuss this more.

The UI install documentation assumes that you've never installed Kubefirst before

True caused it's either the case, or if you did, you should have deprovisioned before trying to create a new cluster. If you think there is something to clarify there, you can discuss more, or create an issue about it in the docs repository, and we can discuss it there :)

the failure of the kubefirst launch up command doesn't provide any information on why it's failing

I think the issue is happening when there are some K3d resources that weren't destroyed correctly for whatever reasons. I think it's hard to define in that case if it's

1. wanted, because the user created a new cluster and is running again the installer.
2. unwanted, because the user struggles with the deprovision process.

[bil9000]

I got a similar error to Carrie when I was running it for the first time. In my case I think it was missing some dependencies, but the error was the same. It would be great if we could be a bit more specific in what went wrong: including "you forgot to delete the old directories/containers" and "you are missing a dependency"