Error map

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

Open the full error page →

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

2 · Network 6 · Platform & cloud 7 · Build & delivery
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…The process '/usr/bin/git' failed with exit code 128 — GitHub Actions: Error: The process '/usr/bin/git' failed with exit code 128 (CI/CD)The process '/usr/b…Resource not accessible by integration — GitHub Actions: Error: Resource not accessible by integration (403) (CI/CD)Resource not access…No hosted parallelism — Azure Pipelines: No hosted parallelism has been purchased or granted (Azure)No hosted paralleli…publickey — Git: Permission denied (publickey). fatal: Could not read from remote repository. (Git)publickeyRepository not found — remote: Repository not found. fatal: repository 'https://github.com/x/y.git/' not found (Git)Repository not foundgithub-actions[bot] 403 — remote: Permission to owner/repo.git denied to github-actions[bot]. fatal: unable to access … The requested URL returned error: 403 (Git)github-actions[bot]…EACCES — npm ERR! code EACCES — permission denied (npm)EACCESdaemon — Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? (Docker)daemon403 — HTTP 403 Forbidden (HTTP)403shallow update not allowed — ! [remote rejected] main -> main (shallow update not allowed) (Git)shallow update not …npm ci out of sync — npm ERR! `npm ci` can only install packages when your package.json and package-lock.json are in sync (npm)npm ci out of syncnpm ci no lockfile — npm ERR! The `npm ci` command can only install with an existing package-lock.json or npm-shrinkwrap.json (npm)npm ci no lockfile

Directly related (3)

The process '/usr/bin/git' failed with exit code 128CI/CD

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…

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).

No hosted parallelismAzure

Azure Pipelines: No hosted parallelism has been purchased or granted

The Azure DevOps organization has no Microsoft-hosted parallel jobs, so pipelines can’t run on hosted agents.

Two steps away (9)

publickeyGit

Git: Permission denied (publickey). fatal: Could not read from remote repository.

SSH authentication to GitHub/GitLab/Bitbucket failed — no key, wrong key, or the key isn’t added to your account.

Repository not foundGit

remote: Repository not found. fatal: repository 'https://github.com/x/y.git/' not found

GitHub/GitLab says the repository doesn’t exist — or you lack access to a private repo.

github-actions[bot] 403Git

remote: Permission to owner/repo.git denied to github-actions[bot]. fatal: unable to access … The requested URL returned error: 403

A GitHub Actions workflow tried to push but the GITHUB_TOKEN doesn’t have write permission.

EACCESnpm

npm ERR! code EACCES — permission denied

npm can’t write to a directory — usually global installs into a root-owned folder.

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.

403HTTP

HTTP 403 Forbidden

The server understood the request but refuses to authorize it — you (or the server process) are not allowed to access this resour…

shallow update not allowedGit

! [remote rejected] main -> main (shallow update not allowed)

You pushed from a shallow clone to a remote that doesn’t accept shallow history.

npm ci out of syncnpm

npm ERR! `npm ci` can only install packages when your package.json and package-lock.json are in sync

package-lock.json doesn’t match package.json, so npm ci refuses to install.

npm ci no lockfilenpm

npm ERR! The `npm ci` command can only install with an existing package-lock.json or npm-shrinkwrap.json

npm ci needs a committed lockfile and didn’t find one.

Map another error

Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException