Error map

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 · layer 7, Build & delivery

Open the full error page →

Centre: this error. First ring: errors it is linked with (11). 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.

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 conn…Job depends on artifacts that have expired — GitLab CI: This job could not start because it could not retrieve the needed artifacts (dependencies: build). (CI/CD)Job depends on arti…execution took longer than 1h0m0s — GitLab CI: ERROR: Job failed: execution took longer than 1h0m0s seconds (CI/CD)execution took long…Pipeline filtered out by workflow:rules — GitLab CI: No pipeline created — pipeline filtered out by workflow:rules / "The rules configuration prevented any jobs from being added to the pipeline" (CI/CD)Pipeline filtered o…permission denied /var/run/docker.sock — Jenkins: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock (CI/CD)permission denied /…Container exceeded memory limit — Bitbucket Pipelines: Container 'Build' exceeded memory limit / Docker container exited with code 137 (CI/CD)Container exceeded …Cannot 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…failed to pull image (GitLab) — GitLab CI: ERROR: Job failed: failed to pull image "registry.example.com/app:latest" with specified policies [always]: access forbidden (CI/CD)failed to pull imag…ERROR: Job failed: exit code 1 — GitLab CI: ERROR: Job failed: exit code 1 (CI/CD)ERROR: Job failed: …runner registration token invalid — GitLab CI: ERROR: Registering runner... failed runner=abc status=couldn't execute POST against https://gitlab.com/api/v4/runners: 403 Forbidden (CI/CD)runner registration…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…deprecated version of actions/upload-artifact — GitHub Actions: Error: This request has been automatically failed because it uses a deprecated version of `actions/upload-artifact: v3` (CI/CD)deprecated version …Unable to download artifact — GitHub Actions: Error: Unable to download artifact(s): Artifact not found for name: build (CI/CD)Unable to download …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…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…Too long with no output — CircleCI: Too long with no output (exceeded 10m0s): context deadline exceeded (CI/CD)Too long with no ou…workflow not triggering — GitHub Actions: workflow does not run on push / pull_request / workflow_dispatch button missing (CI/CD)workflow not trigge…daemon — Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? (Docker)daemonWaiting for next available executor — Jenkins: Still waiting to schedule task — Waiting for next available executor / 'agent1' is offline (CI/CD)Waiting for next av…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…Process completed with exit code 137 — GitHub Actions: Error: Process completed with exit code 137 (Killed — out of memory) (CI/CD)Process completed w…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 …Cannot find orb — CircleCI: Cannot find orb 'circleci/node@9.9.9'. Check the namespace and version exist (CI/CD)Cannot find orbdenied — denied: requested access to the resource is denied (docker push) (Docker)deniedResource not accessible by integration — GitHub Actions: Error: Resource not accessible by integration (403) (CI/CD)Resource not access…Cache not found / Unable to reserve cache — GitHub Actions: Cache not found for input keys: npm-Linux-abc123 / Failed to save: Unable to reserve cache with key, another job may be creating this cache (CI/CD)Cache not found / U…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…Invalid workflow file — GitHub Actions: Invalid workflow file: .github/workflows/ci.yml#L12 — You have an error in your yaml syntax on line 12 (CI/CD)Invalid workflow fi…Process completed with exit code 1 — GitHub Actions: Error: Process completed with exit code 1. (CI/CD)Process completed w…Process completed with exit code 127 — GitHub Actions: Error: Process completed with exit code 127 — command not found (CI/CD)Process completed w…The runner has received a shutdown signal — GitHub Actions: The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled (CI/CD)The runner has rece…No space left on device (runner) — GitHub Actions: System.IO.IOException: No space left on device — the runner's disk is full (CI/CD)No space left on de…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…

Directly related (11)

Job depends on artifacts that have expiredCI/CD

GitLab CI: This job could not start because it could not retrieve the needed artifacts (dependencies: build).

A job needs artifacts from an earlier job, but that job failed, was skipped or its artifacts have expired or been deleted.

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.

Pipeline filtered out by workflow:rulesCI/CD

GitLab CI: No pipeline created — pipeline filtered out by workflow:rules / "The rules configuration prevented any jobs from being added to the pipeline"

Your `workflow:rules` or job-level `rules:` evaluated to "never" for this event, so GitLab created no pipeline or no jobs.

permission denied /var/run/docker.sockCI/CD

Jenkins: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock

The Jenkins user is not allowed to talk to Docker — it is not in the `docker` group or the socket is not mounted in the container.

Container exceeded memory limitCI/CD

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

A Bitbucket Pipelines step used more memory than the step allows (4 GB by default, 1 GB for service containers) and was killed.

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.

failed to pull image (GitLab)CI/CD

GitLab CI: ERROR: Job failed: failed to pull image "registry.example.com/app:latest" with specified policies [always]: access forbidden

The runner could not pull the job's Docker image — authentication, a wrong name or tag, or a registry rate limit.

ERROR: Job failed: exit code 1CI/CD

GitLab CI: ERROR: Job failed: exit code 1

The last command in the job's `script` returned a non-zero status; the real error is printed earlier in the job log.

runner registration token invalidCI/CD

GitLab CI: ERROR: Registering runner... failed runner=abc status=couldn't execute POST against https://gitlab.com/api/v4/runners: 403 Forbidden

`gitlab-runner register` was rejected — the registration token is invalid or expired, or GitLab now expects an authentication tok…

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.

Two steps away (23)

deprecated version of actions/upload-artifactCI/CD

GitHub Actions: Error: This request has been automatically failed because it uses a deprecated version of `actions/upload-artifact: v3`

Since January 2025 the v3 artifact actions no longer work — upload and download steps fail until you move to v4.

Unable to download artifactCI/CD

GitHub Actions: Error: Unable to download artifact(s): Artifact not found for name: build

`download-artifact` could not find an artifact with that name in the run (or repository) — it was never uploaded, named different…

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.

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.

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.

workflow not triggeringCI/CD

GitHub Actions: workflow does not run on push / pull_request / workflow_dispatch button missing

A workflow file exists but no run appears — the trigger filters do not match, the file is not on the right branch, or the workflo…

daemonDocker

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

The docker CLI can’t talk to the Docker engine — it isn’t running, or your user can’t access the socket.

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.

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.

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.

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…

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.

deniedDocker

denied: requested access to the resource is denied (docker push)

You’re logged in, but not allowed to push to that repository — usually the image isn’t tagged with your own username/organisation.

Resource not accessible by integrationCI/CD

GitHub Actions: Error: Resource not accessible by integration (403)

The workflow’s GITHUB_TOKEN doesn’t have the permission needed for that API call (comment, push, create release, write packages).

Cache not found / Unable to reserve cacheCI/CD

GitHub Actions: Cache not found for input keys: npm-Linux-abc123 / Failed to save: Unable to reserve cache with key, another job may be creating this cache

`actions/cache` either found nothing for your key (restore miss) or could not save because another run is already saving the same…

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.

Invalid workflow fileCI/CD

GitHub Actions: Invalid workflow file: .github/workflows/ci.yml#L12 — You have an error in your yaml syntax on line 12

GitHub could not parse your workflow YAML, so no run was created — usually indentation, a tab, or an unquoted special character.

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.

Process completed with exit code 127CI/CD

GitHub Actions: Error: Process completed with exit code 127 — command not found

The shell could not find the command you tried to run: it is not installed on the runner, not on PATH, or misspelled.

The runner has received a shutdown signalCI/CD

GitHub Actions: The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled

The machine running your job was shut down or reclaimed while the job was running — a self-hosted runner stopped, a spot instance…

No space left on device (runner)CI/CD

GitHub Actions: System.IO.IOException: No space left on device — the runner's disk is full

The job filled the runner's disk (about 14 GB free on standard Linux runners): large Docker images, caches, build outputs or test…

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…