Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Troubleshooting

SymptomLook at
Controller in CrashLoopBackOffkubectl -n gitimage-system logs deploy/gitimage-controller --previous: IsolationUnavailable names the failing mode; kubectl -n gitimage-system logs job/gitimage-isolation-check-<hash>
Pod stays SchedulingGatedkubectl get gi <name>: no image yet; kubectl describe pod: GitImageNotFound or build progress Events
Failed / ResolveFailedwrong URL, ref, credentials or host key (host key ... not in known_hosts)
Failed / PodCreationFailedthe namespace’s Pod Security level: label it pod-security.kubernetes.io/enforce=privileged (baseline with rootfulInSandbox)
Failed / ReconcileErrorthe message is the API server’s answer to the controller (an invalid Job, a quota, missing RBAC); the controller log has the same error
Failed / BuildFailedkubectl logs job/<name>-<sha7> -c buildkit
Failed / PushFailedcontroller logs (storage errors), then the build log
Annotated pod is created without a gate or digestkubectl get mutatingwebhookconfiguration gitimage -o yaml: caBundle set? webhook pods ready?
Every build spends ~2 min in load metadata for docker.io/...a registry mirror build pods cannot reach, often one behind an in-cluster ingress controller: In-cluster registry mirrors
Pull fails in s3 modekubectl -n gitimage-system get ds gitimage-node: NotReady means S3 is unreachable or port 25050 in use on 127.0.0.1

Logs are JSON by default; --set logFormat=text for humans, logLevel=info,gitimage=debug for more.