Error map
ERROR: Job failed: exit code 1 GitLab CI: ERROR: Job failed: exit code 1
CI/CD · layer 7, Build & delivery
Centre: this error. First ring: errors it is linked with (7). 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.
Directly related (7)
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.
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…
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.
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.
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.
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.
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 (18)
bash: command not found
The shell can’t find an executable with that name in any directory on your PATH.
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.
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…
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: ERROR: Job failed: execution took longer than 1h0m0s seconds
The job ran past its timeout (project default is 60 minutes) and GitLab killed it.
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.
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.
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…
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).
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.
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.
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.
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.
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…
GitHub Actions: Error: The process '/usr/bin/git' failed with exit code 128
A git command inside the workflow failed — usually authentication to a private repo/submodule, a missing ref, or pushing without…
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.
GitHub Actions: Error: Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
`aws-actions/configure-aws-credentials` found no usable credentials — no keys, no role to assume, or the OIDC token was not reque…
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…
Map another error
Popular: 403500400ORA-00933Critical error1064FileNotFoundException assemblyTypeError