Error map

Container exceeded memory limit Bitbucket Pipelines: Container 'Build' exceeded memory limit / Docker container exited with code 137

CI/CD · layer 7, Build & delivery

Open the full error page →

Centre: this error. First ring: errors it is linked with (8). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.

4 · Application & API 6 · Platform & cloud 7 · Build & delivery
Container exceeded memory limit — Bitbucket Pipelines: Container 'Build' exceeded memory limit / Docker container exited with code 137 (CI/CD)Container e…Cannot connect to the Docker daemon (GitLab) — GitLab CI: Cannot connect to the Docker daemon at tcp://docker:2375. Is the docker daemon running? (CI/CD)Cannot connect to t…Waiting for next available executor — Jenkins: Still waiting to schedule task — Waiting for next available executor / 'agent1' is offline (CI/CD)Waiting for next av…Config compilation failed — CircleCI: Error calling workflow: 'build'. Cannot find a definition for job named test / Config does not conform to schema (CI/CD)Config compilation …ComparisonError: manifest generation failed — Argo CD: ComparisonError: rpc error: code = Unknown desc = Manifest generation error (cached): kustomize build failed (CI/CD)ComparisonError: ma…Process completed with exit code 137 — GitHub Actions: Error: Process completed with exit code 137 (Killed — out of memory) (CI/CD)Process completed w…Too long with no output — CircleCI: Too long with no output (exceeded 10m0s): context deadline exceeded (CI/CD)Too long with no ou…Template file not found — Azure Pipelines: /azure-pipelines.yml: File /templates/build.yml not found in repository / Unable to find template (CI/CD)Template file not f…Cannot find orb — CircleCI: Cannot find orb 'circleci/node@9.9.9'. Check the namespace and version exist (CI/CD)Cannot find orbCannot perform an interactive login from a non TTY device — GitHub Actions: Error: Cannot perform an interactive login from a non TTY device (CI/CD)Cannot perform an i….gitlab-ci.yml invalid — GitLab CI: Found errors in your .gitlab-ci.yml: jobs:build config contains unknown keys: scripts (CI/CD).gitlab-ci.yml inva…Uploading artifacts: too large archive — GitLab CI: ERROR: Uploading artifacts as "archive" to coordinator... too large archive id=123 responseStatus=413 Request Entity Too Large (CI/CD)Uploading artifacts…This job is stuck because you don't have any active runners — GitLab CI: This job is stuck because you don't have any active runners online or available with any of these tags assigned to them (CI/CD)This job is stuck b…Waiting for a runner to pick up this job — GitHub Actions: Waiting for a runner to pick up this job… (job stays queued — No runner matching the specified labels) (CI/CD)Waiting for a runne…Scripts not permitted to use method — Jenkins: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method java.lang.String toUpperCase (CI/CD)Scripts not permitt…compose validation — docker compose: services.x Additional property y is not allowed / yaml: line N: mapping values are not allowed (Docker)compose validationdepends on undefined service — service "web" depends on undefined service "db": invalid compose project (Docker)depends on undefine…the attribute version is obsolete — WARN: the attribute `version` is obsolete, it will be ignored (Docker)the attribute versi…ImagePullBackOff — Kubernetes: ImagePullBackOff / ErrImagePull (Kubernetes)ImagePullBackOfferror parsing called workflow — GitHub Actions: error parsing called workflow ".github/workflows/ci.yml" -> "org/repo/.github/workflows/build.yml@main": workflow was not found (CI/CD)error parsing calle…No such DSL method — Jenkins: java.lang.NoSuchMethodError: No such DSL method 'dockerBuild' found among steps (CI/CD)No such DSL methodOOMKilled — Kubernetes: OOMKilled (exit code 137) (Kubernetes)OOMKilledheap out of memory — FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory (Node.js)heap out of memoryProcess completed with exit code 1 — GitHub Actions: Error: Process completed with exit code 1. (CI/CD)Process completed w…exceeded the maximum execution time — GitHub Actions: The job running on runner GitHub Actions 12 has exceeded the maximum execution time of 360 minutes (CI/CD)exceeded the maximu…execution took longer than 1h0m0s — GitLab CI: ERROR: Job failed: execution took longer than 1h0m0s seconds (CI/CD)execution took long…service connection could not be found — Azure Pipelines: There was a resource authorization issue: The pipeline is not valid. Could not find a service connection with identifier x (Azure)service connection …API rate limit exceeded — GitHub Actions: HttpError: API rate limit exceeded for installation ID 123456 / secondary rate limit (CI/CD)API rate limit exce…

Directly related (8)

Cannot connect to the Docker daemon (GitLab)CI/CD

GitLab CI: Cannot connect to the Docker daemon at tcp://docker:2375. Is the docker daemon running?

A docker-in-docker job could not reach the `docker:dind` service — it is not started, not privileged, or the TLS/host settings do…

Waiting for next available executorCI/CD

Jenkins: Still waiting to schedule task — Waiting for next available executor / 'agent1' is offline

A Jenkins build is queued because no executor with the required label is free or the agent is offline.

Config compilation failedCI/CD

CircleCI: Error calling workflow: 'build'. Cannot find a definition for job named test / Config does not conform to schema

CircleCI could not compile `.circleci/config.yml` — a workflow refers to a missing job, a key is invalid, or the YAML is malforme…

ComparisonError: manifest generation failedCI/CD

Argo CD: ComparisonError: rpc error: code = Unknown desc = Manifest generation error (cached): kustomize build failed

Argo CD could not render the manifests (Helm, Kustomize or plain YAML) for the application, so it cannot compare Git with the clu…

Process completed with exit code 137CI/CD

GitHub Actions: Error: Process completed with exit code 137 (Killed — out of memory)

The command was killed by the system with SIGKILL (128 + 9), almost always because the runner ran out of memory.

Too long with no outputCI/CD

CircleCI: Too long with no output (exceeded 10m0s): context deadline exceeded

A CircleCI step printed nothing for 10 minutes, so CircleCI assumed it hung and cancelled it.

Template file not foundCI/CD

Azure Pipelines: /azure-pipelines.yml: File /templates/build.yml not found in repository / Unable to find template

The YAML references a template (`template: templates/build.yml`) that Azure cannot find — wrong path, repo resource or branch.

Cannot find orbCI/CD

CircleCI: Cannot find orb 'circleci/node@9.9.9'. Check the namespace and version exist

The orb reference in your config does not resolve: wrong namespace, name or version, or the orb is private and not accessible.

Two steps away (19)

Cannot perform an interactive login from a non TTY deviceCI/CD

GitHub Actions: Error: Cannot perform an interactive login from a non TTY device

`docker login` asked for a password interactively, but CI has no terminal — pass credentials non-interactively.

.gitlab-ci.yml invalidCI/CD

GitLab CI: Found errors in your .gitlab-ci.yml: jobs:build config contains unknown keys: scripts

GitLab rejected the pipeline configuration, so no pipeline was created — the message names the job and the problem.

Uploading artifacts: too large archiveCI/CD

GitLab CI: ERROR: Uploading artifacts as "archive" to coordinator... too large archive id=123 responseStatus=413 Request Entity Too Large

The job produced an artifact bigger than the instance or project's maximum artifact size.

This job is stuck because you don't have any active runnersCI/CD

GitLab CI: This job is stuck because you don't have any active runners online or available with any of these tags assigned to them

No GitLab runner can pick up the job — runners are offline, the job’s tags don’t match any runner, or shared runners are disabled.

Waiting for a runner to pick up this jobCI/CD

GitHub Actions: Waiting for a runner to pick up this job… (job stays queued — No runner matching the specified labels)

The job is queued and never starts — no available runner has all the labels in `runs-on`, runners are offline/busy, or the hosted…

Scripts not permitted to use methodCI/CD

Jenkins: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method java.lang.String toUpperCase

A sandboxed Pipeline script called a method that has not been approved in Script Security.

compose validationDocker

docker compose: services.x Additional property y is not allowed / yaml: line N: mapping values are not allowed

The compose file is invalid YAML or uses a key Compose doesn’t recognise at that level (usually an indentation mistake).

depends on undefined serviceDocker

service "web" depends on undefined service "db": invalid compose project

A service lists depends_on (or links/networks) for a service name that isn’t defined in the Compose file(s) being used.

the attribute version is obsoleteDocker

WARN: the attribute `version` is obsolete, it will be ignored

A harmless Compose v2 warning: the top-level version: line in docker-compose.yml is no longer used.

ImagePullBackOffKubernetes

Kubernetes: ImagePullBackOff / ErrImagePull

The node can’t pull the container image — wrong name/tag, missing registry credentials, or registry unreachable.

error parsing called workflowCI/CD

GitHub Actions: error parsing called workflow ".github/workflows/ci.yml" -> "org/repo/.github/workflows/build.yml@main": workflow was not found

A job calls a reusable workflow (`uses: org/repo/.github/workflows/x.yml@ref`) that GitHub cannot find or is not allowed to use.

No such DSL methodCI/CD

Jenkins: java.lang.NoSuchMethodError: No such DSL method 'dockerBuild' found among steps

The Jenkinsfile calls a step that does not exist — the plugin is not installed, or the name or argument is wrong.

OOMKilledKubernetes

Kubernetes: OOMKilled (exit code 137)

The container used more memory than its limit, and the kernel killed it.

heap out of memoryNode.js

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory

The V8 heap hit its limit — a large build (webpack, tsc, Next.js) needs more memory, or the app leaks.

Process completed with exit code 1CI/CD

GitHub Actions: Error: Process completed with exit code 1.

A `run:` command returned a non-zero status, so the step (and job) failed — the real cause is printed in the log lines above.

exceeded the maximum execution timeCI/CD

GitHub Actions: The job running on runner GitHub Actions 12 has exceeded the maximum execution time of 360 minutes

A job ran longer than its time limit — your `timeout-minutes`, or the 6-hour (360 minute) platform limit — and was cancelled.

execution took longer than 1h0m0sCI/CD

GitLab CI: ERROR: Job failed: execution took longer than 1h0m0s seconds

The job ran past its timeout (project default is 60 minutes) and GitLab killed it.

service connection could not be foundAzure

Azure Pipelines: There was a resource authorization issue: The pipeline is not valid. Could not find a service connection with identifier x

The pipeline references a service connection that doesn’t exist in the project or isn’t authorized for this pipeline.

API rate limit exceededCI/CD

GitHub Actions: HttpError: API rate limit exceeded for installation ID 123456 / secondary rate limit

Your workflow (or an action it uses) made too many GitHub API calls and was throttled with 403/429.

Map another error

Popular: 403500400ORA-00933Critical error1064FileNotFoundException assemblyTypeError