{"record":{"id":"c1c4ecdeb390c8bd","repo":"abiosoft/colima","slug":"error-starting-s-w-c1c4ec","errorCode":null,"errorMessage":"error starting %s: %w","messagePattern":"error starting (.+?): %w","errorType":"exception","errorClass":null,"httpStatus":null,"severity":"error","filePath":"cmd/kubernetes.go","lineNumber":124,"sourceCode":"\tArgs: cobra.NoArgs,\n\tRunE: func(cmd *cobra.Command, args []string) error {\n\t\tapp := newApp()\n\t\tk, err := app.Kubernetes()\n\t\tif err != nil {\n\t\t\treturn err\n\t\t}\n\n\t\tif err := k.Teardown(context.Background()); err != nil {\n\t\t\treturn fmt.Errorf(\"error deleting %s: %w\", kubernetes.Name, err)\n\t\t}\n\n\t\tctx := context.Background()\n\t\tif err := k.Provision(ctx); err != nil {\n\t\t\treturn err\n\t\t}\n\n\t\tif err := k.Start(ctx); err != nil {\n\t\t\treturn fmt.Errorf(\"error starting %s: %w\", kubernetes.Name, err)\n\t\t}\n\n\t\treturn nil\n\t},\n}\n\nfunc init() {\n\troot.Cmd().AddCommand(kubernetesCmd)\n\tkubernetesCmd.AddCommand(kubernetesStartCmd)\n\tkubernetesCmd.AddCommand(kubernetesStopCmd)\n\tkubernetesCmd.AddCommand(kubernetesDeleteCmd)\n\tkubernetesCmd.AddCommand(kubernetesResetCmd)\n}\n","sourceCodeStart":106,"sourceCodeEnd":138,"githubUrl":"https://github.com/abiosoft/colima/blob/c3a5f9184d83a197184f897a9f07eb3c01b3bc88/cmd/kubernetes.go#L106-L138","documentation":"The second phase of `colima kubernetes reset`: teardown and Provision succeeded, but k.Start (booting the k3s cluster) failed. The VM itself is healthy; only cluster startup failed. Common causes surface in the wrapped error: k3s image pull failures, guest CPU/memory pressure, or control-plane port (6443) conflicts.","triggerScenarios":"k.Start failing after successful re-provision: k3s images cannot be pulled (network/proxy/DNS issues inside the guest); insufficient VM cpu/memory for the control plane; k3s in the guest crash-looping after the reset; leftover port binding from the pre-reset cluster.","commonSituations":"Corporate proxy/VPN blocking registry pulls during reset; VM created with small `colima start --cpu 1 --memory 2` defaults; flaky guest networking after host sleep/reset cycles.","solutions":["Retry just the start phase — images are now cached, so `colima kubernetes start` is cheap and often succeeds","If pulls failed, fix guest networking (proxy env, DNS) and retry; check the wrapped error and colima logs","Recreate the VM with more headroom: `colima stop && colima delete && colima start --kubernetes --cpu 4 --memory 6`"],"exampleFix":null,"handlingStrategy":"retry","validationCode":"# cheap retry: images are cached after reset, so just start again\ncolima kubernetes start","typeGuard":null,"tryCatchPattern":"if err := resetCmd.Execute(); err != nil {\n    if strings.Contains(err.Error(), \"error starting Kubernetes\") {\n        // teardown+provision succeeded; only the cluster boot failed -> a plain start retry is safe\n        _ = startCmd.Execute()\n    }\n}","preventionTips":["Give the VM enough cpu/memory for the k3s control plane at `colima start` time","Ensure guest network/proxy/DNS works before resets that must re-pull k3s images"],"tags":["colima","kubernetes","reset","startup","resources"],"backgroundTag":null,"analyzedSha":"c3a5f9184d83a197184f897a9f07eb3c01b3bc88","analyzedAt":"2026-08-15T18:58:08.334Z","schemaVersion":2},"datasetVersion":"2026-08-15T22:17:37.221Z"}