All Errors

This Git error occurs when you try to switch branches, but untracked files in your working directory would be overwritten by files from the target branch. Git prevents the checkout to avoid accidental data loss.

This error occurs when Git detects a lock file indicating another Git process is running. Usually caused by an interrupted Git operation that left a stale .git/index.lock file behind. The fix is to safely remove the lock file after confirming no Git process is actually running.

The detached HEAD state occurs when HEAD points directly to a commit instead of a branch. This is not an error but a warning that any new commits you make will not belong to any branch and could be lost when you switch branches.

This warning appears when you try to delete a branch with `git branch -d` that contains commits not yet merged into your current branch or its upstream. Git is protecting you from accidentally losing work. You can either merge the branch first, verify the commits exist elsewhere, or force delete with `git branch -D`.

This Git status message indicates your working directory has no changes to commit. While not an error, it often confuses developers who expect to see modified files. The message means all tracked files match your last commit and there are no staged changes waiting to be committed.

This error occurs when Docker cannot find a build stage referenced in a COPY --from instruction. The stage name must match exactly with an AS alias defined in a previous FROM instruction.

The port you are trying to bind is already used by another process or container. Find and stop the conflicting process, or use a different port mapping.

ClusterMesh errors occur when Cilium cannot establish multi-cluster connectivity. Common causes include certificate mismatches, missing configuration, and API server connectivity issues.

Docker cannot find or access the image. The image name may be misspelled, the repository is private and requires authentication, or the image does not exist.

The container health check is failing. The application inside may not be ready, the health check command may be misconfigured, or the service has crashed. Check container logs and health check output.

Felix is Calico's policy engine. "Felix not ready" errors indicate liveness probe failures due to timeouts or dataplane issues. Fix by reviewing logs, adjusting probe timings, and ensuring dataplane health.

ArgoCD shows resources as out of sync when the cluster state drifts from the Git repository. This occurs due to auto-generated values, mutating webhooks, or resource normalization. Use ignoreDifferences, sync options, or enable auto-healing to resolve drift issues.

Typha synchronization errors occur when calico-node cannot connect to Typha service. Common causes include service discovery failures, TLS certificate issues, and network connectivity problems.

The file you are trying to COPY does not exist in the build context or is excluded by .dockerignore. Check the file path relative to the Dockerfile and your .dockerignore rules.

The system does not have enough memory to start the container. Free up memory by stopping unused containers, increasing system RAM, or adjusting container memory limits.

This error occurs when Docker Desktop cannot access a host directory you're trying to mount. The path must be added to Docker's file sharing settings before it can be used as a bind mount.

The OCI runtime exec failed error occurs when Docker's container runtime cannot start or execute a process inside a container. This typically happens due to missing executables, incorrect shell paths, containerd/runc bugs, or line ending issues in scripts.

Sync wave errors occur when resources with wave annotations do not apply in the expected order. Fix by properly configuring argocd.argoproj.io/sync-wave annotations and ensuring hooks complete before dependent resources.

This error occurs when running containers built FROM scratch because scratch images contain absolutely nothing - no shell, no libraries, no system files. You must use exec form for CMD/ENTRYPOINT and ensure your binary is statically compiled.

cert-manager certificate issuance fails due to ACME validation errors, invalid issuer configuration, or challenge failures. Fix by verifying issuer status, checking DNS/HTTP validation, and reviewing logs.