Error map
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 · layer 7, Build & delivery
Centre: this error. First ring: errors it is linked with (10). 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 (10)
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.
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: 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.
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.
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: 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.
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…
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 (22)
Git: ! [rejected] … (fetch first) — error: failed to push some refs
The remote branch has commits you don’t have locally, so Git refuses to overwrite them. Pull (merge or rebase) first, then push.
Azure AD (Entra ID): AADSTS700016 Application not found in the directory
The client ID in your sign-in request doesn’t exist in the tenant you’re authenticating against.
HTTP 401 Unauthorized
The request has no valid authentication credentials — you need to log in or send a valid token.
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.
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.
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…
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.
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.
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.
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…
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.
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.
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.
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).
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: 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: 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.
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.
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…
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…
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…
Map another error
Popular: 403500400ORA-00933Critical error1064FileNotFoundException assemblyTypeError