All Errors

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.

Exit code 255 is a generic error code indicating an abnormal container termination. It typically occurs when a process exits with a negative exit code (which gets converted to 255), when SSH connections fail, or when Docker encounters an unspecified fatal error.

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.

BGP peer down indicates that Calico node cannot establish BGP sessions with peers. Common causes include firewall blocking port 179, incorrect peer configuration, or network connectivity issues.

The Docker daemon fails to stop or kill a container with 'unknown error after kill'. This occurs when containers enter an inconsistent state due to AppArmor conflicts, zombie processes, or daemon issues.

Repository authentication fails when ArgoCD cannot connect due to expired credentials, missing SSH keys, or incompatible key algorithms. Fix by verifying credentials, using personal access tokens, and updating SSH key algorithms.

Deployment image pull fails due to invalid image references, missing credentials, network issues, or registry problems. Fix by verifying image name/tag, checking imagePullSecrets, testing network connectivity, and validating registry access.

The 'Container already running' error occurs when you try to start a Docker container that is already in a running state. Use docker exec to access the running container, or stop it first if you need to restart it.

The 'volume is in use' error occurs when Docker prevents you from removing a volume because a container (running or stopped) still references it. Stop and remove the dependent container first, or restart the Docker daemon if the reference is stale.

Certificate not ready errors occur when CertificateSigningRequest approval or signing fails. Fix by verifying CSR status, checking signer configuration, and approving pending requests.

Deployment pods stay in not-ready state due to failing health checks, application crashes, or resource constraints. Fix by debugging pods, adjusting probe settings, fixing application issues, or increasing resources.

Pod replicas don't match the desired count due to pending pods, crashed containers, or scheduling failures. Fix by checking node capacity, debugging pending pods, and fixing application issues.

This error occurs when attempting to pause a Docker container that is not in the running state. You can only pause containers that are actively running - check the container status and start it first if needed.

Nodes run out of disk space, triggering eviction of pods. Fix by cleaning up disk space, configuring proper storage limits, and monitoring disk usage.

DNS service overloaded causing high CPU usage. Fix by scaling DNS pods, tuning cache settings, or switching to CoreDNS.

Container image specified in pod doesn't exist in registry. Fix by verifying image name, checking registry, and using correct image references.

This error occurs when you attempt to unpause a Docker container that is not in a paused state. Check the container's actual status with 'docker ps' and use the appropriate command for its current state.

Container runtime socket access denied. Fix by adding kubelet user to docker group, fixing socket permissions, or using rootless Docker.