Skip to content
🚀

DevOps & Deployment Errors

50 errors

Common devops & deployment errors and how to fix them.

50 / 50

  1. 1

    Container Startup Failure

    The container exits immediately or fails to start, often due to a missing entrypoint, wrong command, or application crash on boot.

  2. 2

    Image Not Found

    Kubernetes or Docker cannot find the specified image, usually because it does not exist, is in the wrong registry, or authentication is missing.

  3. 3

    Port Conflict

    Two containers or processes are trying to use the same port, causing a binding conflict.

  4. 4

    Volume Mount Failure

    The container cannot mount a volume, usually because the source path does not exist, permissions are wrong, or the volume type is misconfigured.

  5. 5

    Permission Denied

    The current user lacks the necessary permissions to execute a command or access a resource.

  6. 6

    OOM Killed

    The container used more memory than its configured limit, so the kernel killed it to protect the system.

  7. 7

    CrashLoopBackOff

    The container starts, crashes, and Kubernetes restarts it — this cycle repeats with increasing back-off delays.

  8. 8

    ImagePullBackOff

    The cluster cannot download the specified image from the registry, usually due to authentication, network, or image name issues.

  9. 9

    Connection Timeout

    The application cannot reach a remote service within the timeout period, usually due to network issues or the service being down.

  10. 10

    DNS Resolution Failure

    DNS cannot find the IP address for the given hostname, usually due to DNS misconfiguration or the hostname not existing.

  11. 11

    Certificate Expired

    The TLS certificate used by a service has passed its expiration date, and clients refuse to connect.

  12. 12

    Configuration Error

    A misconfigured setting — wrong value, missing field, or invalid format — prevents the system from working correctly.

  13. 13

    Environment Variable Missing

    A required environment variable is missing, causing the application to crash or malfunction on startup.

  14. 14

    Dependency Unavailable

    The application cannot start or function because a service it depends on is not running or reachable.

  15. 15

    Health Check Failed

    The health check endpoint returns a non-200 response, so the load balancer or orchestrator stops sending traffic to the service.

  16. 16

    Insufficient Resources

    The cluster does not have enough available CPU or memory to schedule the Pod's requested resources.

  17. 17

    Node Unavailable

    A node in the cluster is down or not ready, reducing capacity and potentially causing Pod failures.

  18. 18

    Pod Scheduling Failed

    The scheduler cannot place the Pod on any node due to taints, resource limits, affinity rules, or node selectors.

  19. 19

    Network Policy Blocked

    A Kubernetes NetworkPolicy denies traffic between the source and destination Pod, causing connection failures.

  20. 20

    RBAC Denied

    RBAC (Role-Based Access Control) rules prevent the user or service account from performing the requested action.

  21. 21

    Helm Template Error

    The Helm Chart's Go templates have a syntax error, reference an undefined value, or produce invalid YAML.

  22. 22

    Terraform State Lock

    Another Terraform process or a stale lock is holding the state lock, preventing the current operation from proceeding.

  23. 23

    CI Pipeline Failed

    A step in the CI pipeline (build, test, lint) returned a non-zero exit code, causing the pipeline to fail.

  24. 24

    Build Timeout

    The build or test step exceeds the configured timeout, causing the CI system to cancel it.

  25. 25

    Deployment Rollback

    The new version of the application is failing, so the deployment is reverted to the previous working version.

  26. 26

    Database Connection Failed

    The application cannot establish a connection to the database, usually because the database is down, unreachable, or credentials are wrong.

  27. 27

    Cache Connection Failed

    The cache server is unreachable, causing the application to fall back to slower data sources or fail entirely.

  28. 28

    Message Queue Error

    The application cannot publish or consume messages from the queue, usually due to the queue being down or misconfigured.

  29. 29

    Log Collection Failed

    The log collector (Fluentd, Filebeat) cannot forward logs to the storage backend, resulting in missing or delayed logs.

  30. 30

    Monitoring Data Lost

    Prometheus or another monitoring system has gaps in collected metrics, usually due to scrape failures or storage issues.

  31. 31

    Container crashes on startup: OOM killed

    Your container was OOM killed — it tried to use more memory than the configured limit.

  32. 32

    Port already in use: container cannot bind

    Your container cannot bind to a port — another process or container is already using it.

  33. 33

    Health check fails: container marked unhealthy

    Your container's health check is failing — the health check command returns a non-zero exit code.

  34. 34

    Volume mount fails: path not found

    Your container cannot mount a volume — the host path specified in the volume mapping does not exist.

  35. 35

    CI pipeline fails: secret not available

    Your CI pipeline fails — a secret or environment variable referenced in the pipeline is not set.

  36. 36

    Docker build fails: base image not found

    Your Docker build fails — the base image in the FROM instruction does not exist or cannot be accessed.

  37. 37

    Deployment rollback: new version fails health checks

    Your new deployment failed health checks — the orchestrator rolled back to the previous working version.

  38. 38

    YAML syntax error: invalid indentation

    Your YAML file has a syntax error — inconsistent or incorrect indentation prevents parsing.

  39. 39

    Dockerfile instruction error: invalid command

    Your Dockerfile has an invalid instruction — the builder cannot parse the Dockerfile.

  40. 40

    Invalid Kubernetes manifest: unknown field

    Your Kubernetes manifest has an unknown field — the API server rejects the resource definition.

  41. 41

    Terraform plan error: resource type not found

    Your Terraform config references an unknown resource type — the provider does not recognize it.

  42. 42

    CI pipeline syntax error: invalid workflow file

    Your CI workflow file has a syntax error — the CI system cannot parse the pipeline definition.

  43. 43

    Missing required environment variable in config

    Your config references an environment variable that is not defined — the application fails to start.

  44. 44

    Image tag :latest used in production

    Your production deployment uses the :latest tag — you cannot guarantee which image version is running.

  45. 45

    No resource limits: container consumes all host resources

    Your container has no resource limits — it can use all available CPU and memory, affecting other containers and the host.

  46. 46

    Secrets in plaintext in config files

    Your config file contains secrets in plaintext — anyone with access to the file can read the credentials.

  47. 47

    No logging strategy: logs lost on container restart

    Your container logs are lost on restart — there is no log persistence or centralized logging.

  48. 48

    Insufficient replicas: single point of failure

    Your service has only one replica — if it fails, the entire feature or application becomes unavailable.

  49. 49

    No backup strategy: data loss on failure

    Your service has no backup strategy — if the storage fails, all data is permanently lost.

  50. 50

    Manual deployment: no CI/CD pipeline

    Your deployment is done manually — there is no automated pipeline to build, test, and deploy consistently.

← Back to errors