You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _docs/kb/articles/stuck-in-validating-docker-daemon.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,4 +20,4 @@ Build not starting, showing only `Validating connection to Docker daemon` in `In
20
20
1. Stop the build and restart it.
21
21
2.[Check for outages here.](https://status.codefresh.io)
22
22
3. If using an on-premise Codefresh instance or a Codefresh hybrid runner on your cluster, please check their status.
23
-
4. Please contact our support team with a link to the build showing the issue, as well as any details you may have. For Codefresh runner issues, please include[a set of runner cluster logs](https://github.com/codefresh-support/hybrid-runner-support).
23
+
4. Please contact our support team with a link to the build showing the issue, as well as any details you may have. For Codefresh runner issues, please include[a set of runner cluster logs](https://github.com/codefresh-io/codefresh-support-package).
Copy file name to clipboardExpand all lines: _docs/kb/support-ticket-examples.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,7 @@ To troubleshoot issues or bugs effectively, Codefresh Support requires a detaile
58
58
1.**Engine and DIND logs** for the failed build:
59
59
- While the build is running, navigate to the cluster, and locate the pods named`engine-[buildID]` and`dind-[buildID]`.
60
60
- Save those logs to a file and attach them to the ticket.
61
-
- Alternatively, you can use the[Codefresh Support Package](https://github.com/codefresh-support/codefresh-support-package){:target="\_blank"} to collect the required data*while the affected build is running and the error message is received*.
61
+
- Alternatively, you can use the[Codefresh Support Package](https://github.com/codefresh-io/codefresh-support-package){:target="\_blank"} to collect the required data*while the affected build is running and the error message is received*.
62
62
1.**Helm values file** (to identify overrides such as images or other configurations).
63
63
64
64
####UI: Slowness and other issues
@@ -84,7 +84,7 @@ To troubleshoot issues or bugs effectively, Codefresh Support requires a detaile
84
84
1.**Ebs-csi pod logs** in the`kube-system` namespace if there are volume issues and you're using`ebs-csi`.
85
85
1. Overview of cluster**scale up/down events** for the relevant timeframe.
86
86
87
-
>Alternatively, to collect the data for 3 through 6, use the[Codefresh Support Package](https://github.com/codefresh-support/codefresh-support-package){:target="\_blank"}.
87
+
>Alternatively, to collect the data for 3 through 6, use the[Codefresh Support Package](https://github.com/codefresh-io/codefresh-support-package){:target="\_blank"}.